Exporter les informations relatives à la campagne
/campaigns/details
Utilisez cet endpoint pour récupérer des informations pertinentes sur une campagne spécifique, qui peuvent être identifiées par le
campaign_id
.
Si vous souhaitez récupérer les données du Canvas, reportez-vous au point de terminaison Exporter les détails du Canvas.
Conditions préalables
Pour utiliser cet endpoint, vous aurez besoin d’une clé API avec l’autorisation campaigns.details
.
Limite de débit
We apply the default Braze rate limit of 250,000 requests per hour to this endpoint, as documented in API rate limits.
Paramètres de demande
Paramètre | Requis | Type de données | Description |
---|---|---|---|
campaign_id |
Requis | Chaîne de caractères | Voir l’identifiant API de la campagne. Vous trouverez l’adresse campaign_id pour les campagnes API sur la page Clés API et sur la page Détails de la campagne dans votre tableau de bord ; vous pouvez également utiliser l’endpoint Exporter la liste des campagnes. |
Exemple de demande
1
2
curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/details?campaign_id={{campaign_identifier}}' \
--header 'Authorization: Bearer YOUR-REST-API-KEY'
Réponses
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Content-Type: application/json
Authorization: Bearer YOUR-REST-API-KEY
{
"message": (required, string) the status of the export, returns 'success' when completed without errors,
"created_at" : (string) the date created as ISO 8601 date,
"updated_at" : (string) the date last updated as ISO 8601 date,
"archived": (boolean) whether this campaign is archived,
"draft": (boolean) whether this campaign is a draft,
"name" : (string) the campaign name,
"description" : (string) the campaign description,
"schedule_type" : (string) the type of scheduling action,
"channels" : (array) the list of channels to send via,
"first_sent" : (string) the date and hour of first sent as ISO 8601 date,
"last_sent" : (string) the date and hour of last sent as ISO 8601 date,
"tags" : (array) the tag names associated with the campaign,
"teams" : (array) the names of the Teams associated with the campaign,
"messages": {
"message_variation_id": (string) { // <=This is the actual id
"channel": (string) the channel type of the message, must be either email, ios_push, webhook, content_card, in-app_message, or sms,
"name": (string) the name of the message in the dashboard (eg., "Variation 1")
... channel-specific fields for this message, see the following messages section ...
}
},
"conversion_behaviors": (array) the conversion event behaviors assigned to the campaign, see the following conversions behavior section.
}
Messages par canal
La réponse messages
contiendra des informations sur chaque message. Voici des exemples de réponses de message pour chaque canal :
Notification push
1
2
3
4
5
6
7
{
"channel": (string) the description of the channel, such as "ios_push" or "android_push"
"alert": (string) the alert body text,
"extras": (hash) any key-value pairs provided,
"title": (string) the alert title text,
"action": (string) action link from click
}
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
{
"channel": "email",
"name": (string) the name of the variant,
"extras": (array) the email extras,
"subject": (string) the subject,
"body": (string) the HTML body,
"from": (string) the from address and display name,
"reply_to": (string) the reply-to for message, if different than "from" address,
"title": (string) the name of the email,
"amp_body": (string) the AMP HTML body,
"preheader": (string) the preheader,
"custom_plain_text": (string) the custom plain text,
"should_inline_css": (boolean) whether there should be inline CSS,
"should_whitespace_header": (boolean) whether there should be a whitespace header,
"email_headers": (array) list of email headers
}
in-app Messages
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
{
"type": (string) the description of in-app message type, such as "survey",
"data": {
"pages": [
{
"header":
{
"text":(string) the display text for the header of the survey,
}
"choices": [
{
"choice_id": (string) the choice identifier,
"text": (string) the display text,
"custom_attribute_key": (string) the custom attribute key,
"custom_attribute_value": (sting) the custom attribute value,
"deleted": (boolean) deleted from live campaign,
},
...
]
}
]
}
}
Cartes de contenu
1
2
3
4
5
{
"channel": "content_cards",
"name": (string) the name of variant,
"extras": (hash) any key-value pairs provided; only present if at least one key-value pair has been set
}
Webhook
1
2
3
4
5
6
7
8
{
"channel": "webhook",
"url": (string) the URL for webhook,
"body": (string) the payload body,
"type": (string) the body content type,
"headers": (hash) the specified request headers,
"method": (string) the HTTP method, either POST or GET
}
SMS
1
2
3
4
5
6
{
"channel": "sms",
"body": (string) the payload body,
"from": (string) the list of numbers associated with the subscription group,
"subscription_group_id": (string) the API id of the subscription group targeted in the SMS message
}
Messages types
1
2
3
4
5
6
7
8
9
10
{
"channel": "whats_app",
"subscription_group_id": (string) the API ID of the subscription group selected in the WhatsApp message
"from": (array) the list of strings of the numbers associated with the subscription group,
"template_name": (string) the name of the WhatsApp template being sent,
"template_language_code": (string) the language code of the WhatsApp template being sent,
"header_variables": (array) the list of strings, if present, of Liquid variables being inserted into header of WhatsApp template being sent,
"body_variables": (array) the list of strings, if present, of Liquid variables being inserted into body of WhatsApp template being sent,
"button_variables": (array) the list of strings, if present, of Liquid variables being inserted into buttons of WhatsApp template being sent
}
Messages d’envoi de messages
1
2
3
4
5
6
7
8
9
10
{
"channel": "whats_app",
"subscription_group_id": (string) the API ID of the subscription group selected in the WhatsApp message,
"from": (array) list of strings of the numbers associated with the subscription group,
"layout": (string) the name of the WhatsApp template being sent (text or media or quick-reply),
"header_text": (string, optional) the text, if present, of the header of the message being sent,
"body_text": (string, optional) the text, if present, of the body of the message being sent,
"footer_text": (string, optional) the text, if present, of the footer of the message being sent,
"buttons": (array) list of button objects in the message being sent ({"text": (string) the text of the button})
}
Messages de contrôle
1
2
3
4
{
"channel": (string) the description of the channel that the control is for,
"type": "control"
}
Comportements de conversion
Le tableau conversion_behaviors
contiendra des informations sur chaque comportement relatif aux événements de conversion défini pour la campagne. Ces comportements sont dans l’ordre défini par la campagne. Par exemple, l’événement de conversion A sera le premier élément du tableau, l’événement de conversion B sera le deuxième, etc. Les listes suivantes présentent des exemples de comportement relatif aux événements de conversion :
Clique sur l’e-mail
1
2
3
4
{
"type": "Clicks Email",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours
}
Ouvre l’e-mail
1
2
3
4
{
"type": "Opens Email",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours
}
Achète (tout achat)
1
2
3
4
{
"type": "Makes Any Purchase",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours
}
Achète (produit spécifique)
1
2
3
4
5
{
"type": "Makes Specific Purchase",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
"product": (string) the name of the product, such as "Feline Body Armor"
}
Effectue un événement personnalisé
1
2
3
4
5
{
"type": "Performs Custom Event",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
"custom_event_name": (string) the name of the event, such as "Used Feline Body Armor"
}
Met à niveau l’application
1
2
3
4
5
{
"type": "Upgrades App",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
"app_ids": (array or null) array of app ids, such as ["12345", "67890"], or `null` if "Track sessions for any app" is selected in the UI
}
Utilise l’application
1
2
3
4
5
{
"type": "Starts Session",
"window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
"app_ids": (array or null) array of app ids, such as ["12345", "67890"], or `null` if "Track sessions for any app" is selected in the UI
}
Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section Résolution des problèmes d’exportation.