diff --git a/_docs/_api/identifier_types.md b/_docs/_api/identifier_types.md index 2a15688de57..1121eb0fd57 100644 --- a/_docs/_api/identifier_types.md +++ b/_docs/_api/identifier_types.md @@ -12,12 +12,9 @@ page_type: reference > This reference guide touches on the different types of API identifiers that can be found within the Braze dashboard, their purpose, where you can find them, and how they are typically used. For information on REST API keys or workspace API keys, refer to the [API overview]({{site.baseurl}}/api/api_key/). -The following identifiers can be used to access your template, Canvas, campaign, segment, send or card from the Braze external API. All messages should follow [UTF-8][1] encoding. +The following identifiers can be used to access your template, Canvas, campaign, segment, send or card from the Braze external API. All messages should follow [UTF-8](https://en.wikipedia.org/wiki/UTF-8) encoding. -{% tabs %} -{% tab App IDs %} - -## The app identifier +## App identifier The app identifier or `app_id` is a parameter associating activity with a specific app in your workspace. It designates which app within the workspace you are interacting with. For example, you will find that you will have an `app_id` for your iOS app, an `app_id` for your Android app, and an `app_id` for your web integration. At Braze, you might find that you have multiple apps for the same platform across the various platform types that Braze supports. @@ -25,18 +22,29 @@ The app identifier or `app_id` is a parameter associating activity with a specif There are two ways to locate your `app_id`: -1. Go to **Settings** > **API Keys**. Under **Identification**, you can see every `app_id` that exists for your apps. -2. Go to **Settings** > **APIs and Identifiers**. Your API key is listed next to the **API Key** field in the settings section. +{% tabs local %} +{% tab App Identifiers %} +Go to **Settings** > **APIs and Identifiers** > **App Identifiers**. Your API key for each app is listed under the **Identifier** column. + +{% alert note %} +If you're using the [older navigation]({{site.baseurl}}/navigation), **App Identifiers** is located at **Developer Console** > **API Settings**. +{% endalert %} +{% endtab %} + +{% tab App Settings %} +Go to **Settings** > **App Settings**. Your API key is listed next to the **API Key** field in the settings section. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), these pages are in a new location:
- **API Keys** is located at **Developer Console** > **API Settings**
- **App Settings** located at **Manage Settings** > **Settings** +If you're using the [older navigation]({{site.baseurl}}/navigation), **App Settings** located at **Manage Settings** > **Settings**. {% endalert %} +{% endtab %} +{% endtabs %} ### What can it be used for? App identifiers at Braze are used when integrating the SDK and are also used to reference a specific app in REST API calls. With the `app_id` you can do many things like pull data for a custom event that occurred for a particular app, retrieve uninstall stats, new user stats, DAU stats, and session start stats for a particular app. -{% alert note %} +{% alert tip %} Sometimes, you may find you are prompted for an `app_id` but you are not working with an app, because it is a legacy field specific to a specific platform, you can omit this field by including any string of characters as a placeholder for this required parameter. {% endalert %} @@ -44,7 +52,7 @@ Sometimes, you may find you are prompted for an `app_id` but you are not working During SDK set up, the most common use case for multiple app identifiers is separating those identifiers for debug and release build variants. -To easily switch between multiple app identifier in your builds, we recommend creating a separate `braze.xml` file for each relevant [build variant](https://developer.android.com/studio/build/build-variants.html). A build variant is a combination of build type and product flavor. Note that by default, a new Android project is configured with `debug` and `release` build types and no product flavors. +To easily switch between multiple app identifier in your builds, we recommend creating a separate `braze.xml` file for each relevant [build variant](https://developer.android.com/studio/build/build-variants.html). A build variant is a combination of build type and product flavor. By default, a new Android project is configured with `debug` and `release` build types and no product flavors. For each relevant build variant, create a new `braze.xml` for it in `src//res/values/`: @@ -56,9 +64,6 @@ For each relevant build variant, create a new `braze.xml` for it in `src/
-2. Go to **Settings** > **APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. +{% tabs local %} +{% tab Templates %} +Go to **Templates**, select a template page, then select a pre-existing template. If the template you want does not exist yet, create one and save it. At the bottom of the individual template page, you will be able to find your template identifier. +{% endtab %} + +{% tab API Keys %} +Go to **Settings** > **APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), you can find API identifiers from **Developer Console** > **API Settings**.{% endalert %} +If you're using the [older navigation]({{site.baseurl}}/navigation), you can find API identifiers from **Developer Console** > **API Settings**. +{% endalert %} +{% endtab %} +{% endtabs %} ### What can it be used for? - Update templates over API - Grab information on a specific template -
-{% endtab %} -{% tab Canvas IDs %} - ## Canvas identifier A [Canvas]({{site.baseurl}}/user_guide/engagement_tools/canvas/) identifier or Canvas ID is random key generated by Braze for a given Canvas within the dashboard. Canvas IDs are unique to each Canvas and can be used to reference Canvases through the API. -Note that if you have a Canvas that has variants, there exists an overall Canvas ID as well as individual variant Canvas IDs nested under the main Canvas. +Keep in mind, if you have a Canvas that has variants, there exists an overall Canvas ID as well as individual variant Canvas IDs nested under the main Canvas. ### Where can I find it? + You can find your Canvas ID in the dashboard. Go to **Messaging** > **Canvas** and select a pre-existing Canvas. If the Canvas you want does not exist yet, create one and save it. At the bottom of an individual Canvas page, click **Analyze Variants**. A window appears with the Canvas API identifier located at the bottom. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), **Canvas** is located under **Engagement**. +If you're using the [older navigation]({{site.baseurl}}/navigation), **Canvas** is located under **Engagement**. {% endalert %} ### What can it be used for? + - Track analytics on a specific message - Grab high-level aggregate stats on Canvas performance - Grab details on a specific Canvas - With Currents to bring in user-level data for a "bigger picture" approach to Canvases - With API trigger delivery in order to collect statistics for transactional messages -
-{% endtab %} -{% tab Campaign IDs %} - ## Campaign identifier A [campaign]({{site.baseurl}}/user_guide/engagement_tools/campaigns/) identifier or campaign ID is random key generated by Braze for a given campaign within the dashboard. Campaign IDs are unique to each campaign and can be used to reference campaigns through the API. -Note that if you have a campaign that has variants, there is both an overall campaign ID as well as individual variant campaign IDs nested under the main campaign. +Keep in mind, if you have a campaign that has variants, there is both an overall campaign ID as well as individual variant campaign IDs nested under the main campaign. ### Where can I find it? + You can find your campaign ID one of two ways: -1. Go to **Messaging** > **Campaigns** and select a pre-existing campaign. If the campaign you want does not exist yet, create one and save it. At the bottom of the individual campaign page, you will be able to find your **Campaign API Identifier**.

-2. Go to **Settings** > **APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. +{% tabs local %} +{% tab Campaigns %} +Go to **Messaging** > **Campaigns** and select a pre-existing campaign. If the campaign you want does not exist yet, create one and save it. At the bottom of the individual campaign page, you will be able to find your **Campaign API Identifier**. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), these pages are in a different location:
- **Campaigns** is under **Engagement**
- **API Keys** is located at **Developer Console** > **API Settings** +If you're using the [older navigation]({{site.baseurl}}/navigation), **Campaigns** is under **Engagement**. {% endalert %} +{% endtab %} + +{% tab API Keys %} +Go to **Settings** > **APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. + +{% alert note %} +If you're using the [older navigation]({{site.baseurl}}/navigation), **API Keys** is located at **Developer Console** > **API Settings**. +{% endalert %} +{% endtab %} +{% endtabs %} ### What can it be used for? + - Track analytics on a specific message - Grab high-level aggregate stats on campaign performance - Grab details on a specific campaign @@ -131,23 +152,31 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), these page - With API-triggered delivery in order to collect statistics for transactional messages - To [search for a specific campaign]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns/#search-syntax) on the **Campaigns** page using the filter `api_id:YOUR_API_ID` -
-{% endtab %} -{% tab Segment IDs %} - ## Segment identifier A [segment]({{site.baseurl}}/user_guide/engagement_tools/segments/) identifier or segment ID is random key generated by Braze for a given segment within the dashboard. Segment IDs are unique to each segment and can be used to reference segments through the API. ### Where can I find it? + You can find your segment ID one of two ways: -1. Go to **Audience** > **Segments** and select a pre-existing segment. If the segment you want does not exist yet, create one and save it. At the bottom of the individual segment page, you will be able to find your segment identifier.

-2. Go to **Settings** > ****APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. +{% tabs local %} +{% tab Segments %} +Go to **Audience** > **Segments** and select a pre-existing segment. If the segment you want does not exist yet, create one and save it. At the bottom of the individual segment page, you will be able to find your segment identifier. + +{% alert note %} +If you're using the [older navigation]({{site.baseurl}}/navigation), **Segments** is under **Engagement**. +{% endalert %} +{% endtab %} + +{% tab API Keys %} +Go to **Settings** > ****APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), these pages are in a different location:
- **Segments** is under **Engagement**
- **API Keys** is located at **Developer Console** > **API Settings** +If you're using the [older navigation]({{site.baseurl}}/navigation), **API Keys** is located at **Developer Console** > **API Settings**. {% endalert %} +{% endtab %} +{% endtabs %} ### What can it be used for? - Get details on a specific segment @@ -155,9 +184,6 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), these page - Pull how many times a custom event was recorded for a particular segment - Specify and send a campaign to a members of a segment from within the API -{% endtab %} -{% tab Card IDs %} - ## Card identifier A card identifier or card ID is random key generated by Braze for a given News Feed card within the dashboard. Card IDs are unique to each [News Feed]({{site.baseurl}}/user_guide/engagement_tools/news_feed/) card and can be used to reference cards through the API. @@ -167,37 +193,43 @@ News Feed is being deprecated. Braze recommends that customers who use our News {% endalert %} ### Where can I find it? + You can find your card ID one of two ways: -1. Go to **Messaging** > **News Feed** and select a pre-existing News Feed. If the News Feed you want does not exist yet, create one and save it. At the bottom of the individual News Feed page, you will be able to find your unique card identifier.

-2. Go to **Settings** > **APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. +{% tabs local %} +{% tab News Feed %} +Go to **Messaging** > **News Feed** and select a pre-existing News Feed. If the News Feed you want does not exist yet, create one and save it. At the bottom of the individual News Feed page, you will be able to find your unique card identifier. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), these pages are in a new location:
- **News Feed** is under **Engagement**
- **API Keys** is located at **Developer Console** > **API Settings** +If you're using the [older navigation]({{site.baseurl}}/navigation), **News Feed** is under **Engagement**. {% endalert %} +{% endtab %} + +{% tab API Keys %} +Go to **Settings** > **APIs and Identifiers**. Here, Braze offers an **Additional API Identifiers** search where you can look up specific identifiers. + +{% alert note %} +If you're using the [older navigation]({{site.baseurl}}/navigation), **API Keys** is located at **Developer Console** > **API Settings**. +{% endalert %} +{% endtab %} +{% endtabs %} ### What can it be used for? + - Retrieve relevant information on a card - Track events related to Content Cards and engagement -
-{% endtab %} -{% tab Send IDs %} - ## Send identifier A send identifier, or send ID, is a key either generated by Braze or created by you for a given message send under which the analytics should be tracked. The send identifier allows you to pull back analytics for a specific instance of a campaign send through the [`/sends/data_series` endpoint]({{site.baseurl}}/api/endpoints/export/campaigns/get_send_analytics/). ### Where can I find it? + API and API triggered campaigns that are sent as a broadcast will automatically generate a send identifier if a send identifier is not provided. If you want to specify your own send identifier, you will have to first create one through the [`/sends/id/create` endpoint]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_create_send_ids/). The identifier must be all ASCII characters and at most 64 characters long. You can reuse a send identifier across multiple sends of the same campaign if you want to group analytics of those sends together. ### What can it be used for? Send and track message performance programmatically, without campaign creation for each send. -
-{% endtab %} -{% tab Subscription group IDs %} - ## Subscription group identifier A subscription group identifier, or subscription group ID, is a key generated by Braze for a given subscription group. IDs are unique to each subscription group and can be used to reference subscription groups through the API. @@ -211,9 +243,3 @@ Go to **Audience** > **Subscriptions** and copy the ID next to the respective su - List a user's subscription groups - Grab a user's subscription group status - Update a user's subscription group status - -{% endtab %} -{% endtabs %} - -[1]: https://en.wikipedia.org/wiki/UTF-8 -[3]: https://developer.android.com/studio/build/build-variants.html diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md index 511164b54d6..63e5910a4d9 100644 --- a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md +++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md @@ -1637,7 +1637,7 @@ This event occurs when an SMS is sent to the carrier. "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas, "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas, "canvas_step_name": (optional, string) name of the Canvas step this event belongs to, - "send_id": (optional, string) message send ID this message belongs to + "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only) } ``` {% endapi %} @@ -1650,7 +1650,7 @@ This event occurs when an SMS is sent to the carrier. SMS, Delivery {% endapitags %} -This event occurs when an SMS was successfully delivered to the users mobile phone. +This event occurs when an SMS was successfully delivered to the user's mobile phone. ```json // SMS Delivery: users.messages.sms.Delivery @@ -1675,7 +1675,7 @@ This event occurs when an SMS was successfully delivered to the users mobile pho "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas, "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas, "canvas_step_name": (optional, string) name of the Canvas step this event belongs to, - "send_id": (optional, string) message send ID this message belongs to + "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only) } ``` {% endapi %} @@ -1715,7 +1715,7 @@ This event occurs when an SMS send gets rejected by the carrier, this can happen "message_variation_name": (optional, string) the name of the message variation if from a campaign, "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas, "canvas_step_name": (optional, string) name of the Canvas step this event belongs to, - "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types) + "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only) } ``` {% endapi %} @@ -1755,7 +1755,7 @@ This event occurs when an SMS experiences delivery failure. Use this event and t "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas, "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas, "canvas_step_name": (optional, string) name of the Canvas step this event belongs to, - "send_id": (optional, string) message send ID this message belongs to + "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only) } ``` {% endapi %} diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md index 896bbaa8edf..516265ffa5d 100644 --- a/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md +++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md @@ -161,7 +161,7 @@ Property values can be any of the following data types: | Nested objects | Objects that are inside of other objects. For more, see the section in this article on [Nested objects](#nested-objects). {: .reset-td-br-1 .reset-td-br-2} -Event property objects that contain array or object values can have an event property payload up to 50 KB. +Event property objects that contain array or object values can have an event property payload up to 100 KB. You can change the data type of your custom event property, but be aware of the impacts of [changing data types]({{site.baseurl}}/help/help_articles/data/change_custom_data_type/) after data has been collected. diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md index 2427f43bfa0..6585b93be60 100644 --- a/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md +++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md @@ -15,7 +15,7 @@ You can use nested objects—objects that are inside of another object—to send ## Limitations - Nested data is supported for both [custom events]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) and [purchase events]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/), but not other event types. -- Event property objects that contain array or object values can have an event property payload of up to 50 KB. +- Event property objects that contain array or object values can have an event property payload of up to 100 KB. - Event property schemas cannot be generated for purchase events. - Event property schemas are generated through sampling custom events from the last 24 hours. @@ -172,7 +172,7 @@ There is no change in how we charge data points as a result of adding this capab ### How much nested data can be sent? -If one or more of the event's properties contains nested data, the maximum payload for all combined properties on an event is 50 KB. Any request over that size limit will be rejected. +If one or more of the event's properties contains nested data, the maximum payload for all combined properties on an event is 100 KB. Any request over that size limit will be rejected. [4]: {% image_buster /assets/img_archive/nested_event_properties_segmentation.png %} [5]: {% image_buster /assets/img_archive/nested_event_properties_personalization.png %} diff --git a/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md b/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md index 48943a2a8aa..fddcd843aeb 100644 --- a/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md +++ b/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md @@ -42,13 +42,16 @@ You will see the following segment statistics, which update in real-time as you You can see how one segment is performing compared to another across a set of pre-selected KPIs by visiting the [Segment Insights]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_insights/) page of your dashboard. -### Messaging use and historical membership +### Messaging use +The **Messaging Use** section shows which segments, currently enabled campaigns, and currently enabled canvases are targeting your segment. -The **Messaging Use** section shows which campaigns have targeted your segment, while the **Historical Membership** section shows how the size of your segment changed over time. Use the dropdown to filter segment membership by date range. +![Under Messaging Use, view the campaigns that your segment is being used in.][4] + +### Historical membership +The **Historical Membership** section shows how the size of your segment changed over time. Use the dropdown to filter segment membership by date range. The historical segment membership count is an estimate, similar to how the segment size is an estimate before you click **Calculate Exact Statistics**. Braze estimates the membership count by querying users in a random bucket range. This means that on one day, the membership count could be based on users with a random bucket number of 111–120, and on another day, users with a random bucket number of 8,452–8,455. Therefore, the graph might show slight fluctuations on each date due to different amounts of users landing within the random bucket ranges. -![Under Messaging Use, view the campaigns that your segment is being used in.][4] ![Use the Historical Membership dropdown to filter segment membership by date range.][10] ### User preview diff --git a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns.md b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns.md index 903549820b7..a0325aa4253 100644 --- a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns.md +++ b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns.md @@ -34,7 +34,7 @@ guide_featured_list: guide_menu_title: "Additional resources" guide_menu_list: - name: AI Copywriting Assistant - link: /docs/user_guide/intelligence/ai_copywriting/ + link: /docs/user_guide/brazeai/generative_ai/ai_copywriting/ image: /assets/img/braze_icons/edit-05.svg --- diff --git a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/targeting_users.md b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/targeting_users.md index 10a2c3fcc21..8af1023d7ea 100644 --- a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/targeting_users.md +++ b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/targeting_users.md @@ -65,13 +65,16 @@ For more information and best practices, refer to [Multivariate & A/B Testing][4 Braze provides detailed audience statistics of the targeted channels in the footer. -For campaigns, select **Calculate Exact Statistics** to determine an accurate number for your reachable users as this will search through every user in your user base. The number of reachable users may decrease if you use a [Global Control Group]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/) or set up message eligibility. +The larger your user base is, the more likely the **Reachable Users** amount is a rough estimate. The number of reachable users may decrease if you use a [Global Control Group]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/) or set up message eligibility. Select [Calculate exact statistics]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment#calculating-exact-statistics) to determine an accurate number for your reachable users as this will search through every user in your user base. -For segments, the larger your user base is, the more likely the **Reachable Users** amount is a rough estimate. For more details, refer to [Calculating exact statistics]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment#calculating-exact-statistics). +Note that: + +- Calculating exact statistics can take a few minutes to run. This function only calculates the exact statistics at the segment level, not at the filter or filter group level. +- For large segments, it is normal to see slight variation even when calculating exact statistics. The accuracy of this feature is expected to be 99.999% or greater. ![][24] -In order to see what percentage of your user base is being targeted or the Lifetime Value (LTV) for this segment, click **Show Additional Stats** located after the statistics footer. +To see what percentage of your user base is being targeted or the Lifetime Value (LTV) for this segment, select **Show Additional Statistics**. [1]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign/ [2]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/ diff --git a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md index 72a083e707e..0ab14e5fab1 100644 --- a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md +++ b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md @@ -11,7 +11,9 @@ description: "This reference article covers time-based functionalities for campa > When using campaigns, you can use the time-based scheduling options to reach your audience. These time-based functionalities include campaigns that are set to scheduled delivery and action-based delivery. -You can also check out our [Campaign Setup](https://learning.braze.com/campaign-setup-delivery-targeting-conversions) Braze Learning course for more on campaign delivery. +{% alert tip %} +For more on campaign delivery, check out our dedicated [Campaign Setup](https://learning.braze.com/campaign-setup-delivery-targeting-conversions) Braze Learning course. +{% endalert %} ## Scheduled delivery @@ -76,7 +78,7 @@ When choosing your delay length, keep in mind that if you set a delay that is lo | Definition | Time Zone | | ---------- | --------- | -| Send message after a delay. You can specify a delay in seconds, minutes, hours, days, or weeks. | N/A | +| Send message after a delay. You can specify a delay in seconds, minutes, hours, days, or weeks. For [in-app message campaigns]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about), you can set a delay up to two hours only. | N/A | {: .reset-td-br-1 .reset-td-br-2} ![Schedule Delay set to send campaign after one day after the trigger event occurs.][7] diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas.md index cb912ac86d1..25eee7956f0 100644 --- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas.md +++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas.md @@ -49,6 +49,6 @@ guide_featured_list: guide_menu_title: "Additional resources" guide_menu_list: - name: AI Copywriting Assistant - link: /docs/user_guide/intelligence/ai_copywriting/ + link: /docs/user_guide/brazeai/generative_ai/ai_copywriting/ image: /assets/img/braze_icons/edit-05.svg --- diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md index 76e95c05b20..d079c3326c6 100644 --- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md +++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md @@ -150,7 +150,7 @@ After adding segments and filters to your target audience, you can test if your ![]({% image_buster /assets/img_archive/user_lookup.png %}){: style="max-width:50%;"} -#### Adjust entry controls +#### Selecting entry controls Entry controls determine if users are allowed to re-enter a Canvas. You can also limit the number of people who would potentially enter this Canvas. For example, if you set the **Maximum users to potentially enter this Canvas** field to 1,000 users, and select the **Limit everytime the Canvas is scheduled** checkbox, then the Canvas will sent to 1,000 users per day. @@ -162,6 +162,19 @@ Braze doesn't recommend using the **Limit everytime the Canvas is scheduled** fe Setting the [exit criteria]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/exit_criteria) determines which users you want to exit a Canvas. If a user performs the exception event or matches the segments and filters, they won't receive any further messages. +#### Calculating target population + +In the **Target Population** section, you can view a summary of your audience, such as your selected segments and additional filters, and a breakdown of how many users are reachable per messaging channel. To calculate the exact number of reachable users in your target audience instead of the default estimation, select [Calculate exact statistics]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment#calculating-exact-statistics). + +Note that: + +- Calculating exact statistics can take a few minutes to run. This function only calculates the exact statistics at the segment level, not at the filter or filter group level. +- For large segments, it is normal to see slight variation even when calculating exact statistics. The accuracy of this feature is expected to be 99.999% or greater. + +To view additional statistics, such as the average lifetime revenue for targeted users, select **Show Additional Statistics**. + +![Target Population breakdown with option to cacluate exact statistics.][2] + ### Step 2d: Select your send settings Select **Send Settings** to edit your subscription settings, turn on rate limiting, and to turn on Quiet Hours. By turning on [rate limiting][6b] or [frequency capping][6c], you can ease the marketing pressure placed on your users and ensure you aren't over messaging them. @@ -327,7 +340,8 @@ Need to make edits to your Canvas after launch? Well, you can! Check out [Editin {% endalert %} -[1]:{% image_buster /assets/img_archive/canvas_dropdown.png %} +[1]: {% image_buster /assets/img_archive/canvas_dropdown.png %} +[2]: {% image_buster /assets/img_archive/canvas_exact_stats.png %} [3]: {% image_buster /assets/img_archive/choose_canvas_experience.png %} [6b]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#rate-limiting-and-canvas-components [6c]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting#frequency-capping diff --git a/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist.md b/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist.md index e67c3073328..e03b446d2ea 100644 --- a/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist.md +++ b/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist.md @@ -64,7 +64,7 @@ For a Message component in multi-channel messaging, we recommend the following: You've launched your Canvas! Now, what? Use this checklist to see how you can review and adjust your Canvas in the event of discrepancies after launch based on these scenarios. -### Lots of entries, but few sends +### Many entries, but few sends For example, let's say that you've noticed a disparity between your number of messages sent versus total entries. You can identify and uncover areas to adjust your Canvas by checking these key areas. @@ -82,7 +82,7 @@ Review the distribution of users between your variants and your control group. I ### An empty total audience -If you're noticing that messages have been sent, but aren't seeing any entry data for your Canvas, the main reason that users may not be entering your Canvas can be due to race conditions and restrictive audience segmentation filters. +If you aren’t seeing any entry data for your Canvas, the reason that users may not be entering your Canvas can be due to race conditions and restrictive audience segmentation filters. If you're using action-based entry in your entry schedule, check that you haven't used the same trigger action here as in your **Target Audience**. A race condition may occur in which the user is not in the audience at the time they perform the trigger event, which means they won't enter the Canvas. diff --git a/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md b/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md index be9c8e2db04..2436c67d859 100644 --- a/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md +++ b/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md @@ -76,7 +76,9 @@ You can edit these Canvas settings and information after a Canvas launches using * Quiet Hours * Target audience -You can't edit conversion events after a Canvas has launched. +After a Canvas has launched: +- Conversion events can't be edited. +- [Audience paths]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/audience_paths/), [action paths]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/action_paths/), and [experiment paths]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step) can't be added or removed to these steps and can't be reordered to adjust the ranking. As a workaround, edit the active Canvas and duplicate the step, which will be editable until you launch the draft. ### Individual steps @@ -138,11 +140,11 @@ If you update the delay in a Delay step or evaluation window in the Action Paths If you delete a step with a time delay (such as Delay or Action Paths) and decide to redirect those users into another Canvas step, the users will only be redirected after the step's time delay has completed. For example, let's say you delete a Delay step with a one day delay and redirect those users to a Message step. In this case, the users will only be redirected after the one day delay has been completed. -If your Canvas contains one or more [Experiment Paths]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/) steps, deleting steps could invalidate the results of this step. +If your Canvas has one or more Experiment Paths steps, deleting steps could invalidate the results of this step. ### Stopping Canvases -Stopping a Canvas will not exit users who are waiting in a step. If you re-enable the Canvas and the users are still waiting, they will complete the step and move to the next step. However, if the time that the user should've progressed to the next step has passed, they will instead exit the Canvas. +Stopping a Canvas won't exit users who are waiting in a step. If you re-enable the Canvas and the users are still waiting, they will complete the step and move to the next step. However, if the time that the user should've progressed to the next step has passed, they will instead exit the Canvas. For example, let's say you have a Canvas created using the Canvas Flow workflow set to launch at 2 pm with one variant with two steps: a Delay step with a one hour delay that goes into a Message step. diff --git a/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md b/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md index 3b25788acf9..36da9f0f3de 100644 --- a/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md +++ b/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md @@ -76,7 +76,7 @@ The media library acts as your dashboard's centralized location for assets, as a ## Generate an image using AI {#generate-ai} -You can generate images for your media library using [DALL·E 2](https://openai.com/dall-e-2/), an AI system from OpenAI, a Braze third-party provider. This system can create realistic images and art from a description in natural language. Each request generates four variations of your prompt, and your company can generate images 10 times per day. This total applies to all users in your company. +You can generate images for your media library using [DALL·E 3](https://openai.com/index/dall-e-3/), an AI system from OpenAI, a Braze third-party provider. This system can create realistic images and art from a description in natural language. Each request generates four variations of your prompt, and your company can generate images 10 times per day. This total applies to all users in your company. 1. From the media library, select **AI Image Generator**. 2. Enter a description of the image you want to generate, up to 300 characters. The more detailed the description, the better your result. diff --git a/_docs/_user_guide/message_building_by_channel/email/amphtml.md b/_docs/_user_guide/message_building_by_channel/email/amphtml.md index dc5bf55c31e..8677b985d0f 100644 --- a/_docs/_user_guide/message_building_by_channel/email/amphtml.md +++ b/_docs/_user_guide/message_building_by_channel/email/amphtml.md @@ -90,12 +90,12 @@ Refer to these additional resources: {% tabs %} {% tab Essentials %} -These are what makes an AMP HTML email...AMP'ed! Each of these elements is required in the body of your AMP email. +These are what make an AMP HTML email...AMP'ed! Each of these elements is required in the body of your AMP email. | Component | Description | Example | |---------|--------------|---------| | Identification

`⚡4email` or `amp4email`| Identifies your email as an AMP HTML email. | ``
``
`` | -| Load AMP runtime

``| +| Load AMP runtime

``| | CSS Boilerplate | Hides content until AMP is loaded.
Email providers who support AMP emails enforce security checks that only allow vetted AMP scripts to run in their clients. | `` | {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3} @@ -158,18 +158,18 @@ Some examples include: * Dynamically updating items in the feed * Article bookmark email -Using this component, users can submit or clear field values. Also, depending on how you set up your email, you can give additional prompts to users, such as whether or not the survey submission was successful, or render the responses from your users showing results of the survey (such as a voting campaign). +Using this component, users can submit or clear field values. Also, depending on how you set up your email, you can give additional prompts to users, such as whether or not the survey submission was successful, or render the responses from your users showing survey results (such as a voting campaign). {% endtab %} {% tab Collapsable Content %} Expand your content sections using the `` component. This component allows you to display collapsible and expandable content sections providing a way for viewers to glance at the content outline and jump to any section. -If you tend to send long educational articles or personalized recommendations, this provides a way for viewers to glance at the content outline and jump to any section or specific product recommendation to get more details. This can be particularly helpful for mobile users where even a couple of sentences into a section requires scrolling. +If you tend to send long educational articles or personalized recommendations, this provides a way for viewers to glance at the content outline and jump to any section or specific product recommendation to get more details. This can be particularly helpful for mobile users where even a few sentences into a section require scrolling. {% endtab %} {% tab Image Heavy Emails %} -If you tend to send emails with a lot of professional photos like retail brands, you can use the `` component that allows users to engage with an image that appeals to them. When the user clicks the image, this component displays the image in the center of the message creating a lightbox effect. +If you tend to send emails with many professional photos like retail brands, you can use the `` component that allows users to engage with an image that appeals to them. When the user clicks the image, this component displays the image in the center of the message creating a lightbox effect. In addition, the `` component allows the user to view a detailed image description. You can use the same component for more than one image. For example, if you have multiple images included in your email when the user clicks either image, the image displays in the lightbox. diff --git a/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md b/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md index c8b65724bae..c05d1c54099 100644 --- a/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md +++ b/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md @@ -76,17 +76,54 @@ When a Content Block without a `lid` value is inserted into a new message, the l For Content Blocks, Braze recommends creating copies of existing Content Blocks to use in new messages. This can be done by bulk duplicating to prevent scenarios where you might reference a Content Block that has not been enabled for link aliasing in a new message. {% endalert %} -## Examples +## How links are updated with link aliasing -The following table provides examples of links in an email body, link aliasing results, and explanations for how the original link is updated with link aliasing. +The following tables provide examples of links in an email body, link aliasing results, and explanations for how the original link is updated with link aliasing. -| Link in Email Body | Link with Aliasing | Logic | -|---|---|---| -| https://www.braze.com | https://www.braze.com?lid=slfdldtqdhdk | Braze inserts a question mark (?) and adds the first query parameter into the URL. | -| https://www.braze.com?utm_campaign=retention&utm_source=email | https://www.braze.com?utm_campaign=retention&utm_source=email&lid=0goty30mviyz | Braze detects other query parameters and appends `lid=` to the end of the URL. | -| {%raw%}``{%endraw%} | {%raw%}``{%endraw%} | Braze recognizes that this is a URL and already has a question mark (?) present. Then, it appends the `lid` query parameter after the question mark. | -| https://www.braze.com#bookmark1?utm_source=email | https://www.braze.com?lid=eqslgd5a9m3y#bookmark1?utm_source=email | Braze expects the URL to use a standard structure where anchors (#) are present after a question mark (?). Because Braze reads from left to right, we will append the question mark and `lid` value before the anchor. | -{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3} +### Permalink + +**Logic:** Braze inserts a question mark (?) and adds the first query parameter into the URL. + +| Link in Email Body | Link with Aliasing | +|-----------------------|----------------------------------------| +| https://www.braze.com | https://www.braze.com?lid=slfdldtqdhdk | +{: .reset-td-br-1 .reset-td-br-2} + +### Link with more query parameters + +**Logic:** Braze detects other query parameters and appends `lid=` to the end of the URL. + +| Link in Email Body | Link with Aliasing | +|---------------------------------------------------------------|--------------------------------------------------------------------------------| +| https://www.braze.com?utm_campaign=retention&utm_source=email | https://www.braze.com?utm_campaign=retention&utm_source=email&lid=0goty30mviyz | +{: .reset-td-br-1 .reset-td-br-2} + +### HTML link + +**Logic:** Braze recognizes a link is a URL and already has a question mark (?) present, so the `lid` query parameter is appended after the question mark. + +| Link in Email Body | Link with Aliasing | +|-------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| {%raw%}``{%endraw%} | {%raw%}``{%endraw%} | +{: .reset-td-br-1 .reset-td-br-2} + +### Link with anchor + +**Logic:** Braze expects the URL to use a standard structure where anchors (#) are present after a question mark (?). Because Braze reads from left to right, the question mark and `lid` value are appended before the anchor. + +| Link in Email Body | Link with Aliasing | +|--------------------------------------------------|-------------------------------------------------------------------| +| https://www.braze.com#bookmark1?utm_source=email | https://www.braze.com?lid=eqslgd5a9m3y#bookmark1?utm_source=email | +{: .reset-td-br-1 .reset-td-br-2} + +### Link with anchor and capture tag + +**Logic:** When using link aliasing with URLs that contain anchors (#), Braze expects the anchor to be placed after the query parameters. This means that the `lid` value must be appended before the anchor for proper tracking, and since Braze reads the URL from left to right, the question mark (?) and `lid` should come before the anchor. + +| Link in Email Body | Link with Aliasing | +|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| {%raw%}`Check out our special offer!`{%endraw%} | {%raw%}`Check out our special offer!` {%endraw%} | +{: .reset-td-br-1 .reset-td-br-2} ## Link aliasing for URLs generated via Liquid diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md index 7c571bcb5f1..a810b6425ff 100644 --- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md +++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md @@ -8,7 +8,7 @@ description: "This reference page notes the operators that Liquid supports, as w # Operators -Liquid supports many [operators][25] that can be used in your conditional statements. +Liquid supports many [operators][25] that can be used in your conditional statements. Note that parentheses are invalid characters in Liquid and prevents your tags from working. | Syntax| Operator Description| |---------|-----------| diff --git a/_includes/html_include.html b/_includes/html_include.html index df4fa3322ae..3e5530f30c1 100644 --- a/_includes/html_include.html +++ b/_includes/html_include.html @@ -93,7 +93,6 @@ - /assets/js/contentcards.js {% endjavascript_asset_tag %} - diff --git a/_lang/ja/_api/objects_filters/event_object.md b/_lang/ja/_api/objects_filters/event_object.md index 66f0d3d1313..bdb77ce998b 100644 --- a/_lang/ja/_api/objects_filters/event_object.md +++ b/_lang/ja/_api/objects_filters/event_object.md @@ -70,7 +70,7 @@ Braze で既存のユーザープロファイルのみを更新したい場合 | オブジェクト | オブジェクトは文字列として取り込まれる。 | {: .reset-td-br-1 .reset-td-br-2} -配列またはオブジェクト値を含むイベントプロパティオブジェクトには、最大 50 KB のイベントプロパティペイロードを設定できます。 +配列またはオブジェクト値を含むイベントプロパティオブジェクトには、最大 100 KB のイベントプロパティペイロードを設定できます。 ### イベント・プロパティの永続性 イベント・プロパティは、親イベントによってトリガーされるメッセージのフィルタリングと、リキッド・パーソナライゼーションのために設計されている。デフォルトでは、Braze ユーザープロファイルでは永続化されません。セグメンテーションでイベントプロパティ値を使用するには、イベントプロパティ値を長期的に保存するための様々なアプローチについて詳述している[カスタム][5]イベントを参照のこと。 diff --git a/_lang/ja/_api/objects_filters/purchase_object.md b/_lang/ja/_api/objects_filters/purchase_object.md index 3b091e3eed2..e946ae3937a 100644 --- a/_lang/ja/_api/objects_filters/purchase_object.md +++ b/_lang/ja/_api/objects_filters/purchase_object.md @@ -103,7 +103,7 @@ Authorization: Bearer YOUR-REST-API-KEY | オブジェクト | オブジェクトは文字列として取り込まれます。 | {: .reset-td-br-1 .reset-td-br-2} -配列またはオブジェクト値を含むイベントプロパティオブジェクトには、最大 50 KB のイベントプロパティペイロードを設定できます。 +配列またはオブジェクト値を含むイベントプロパティオブジェクトには、最大 100 KB のイベントプロパティペイロードを設定できます。 ### 購入プロパティ diff --git a/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events.md b/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events.md index 37a0cf96f07..4f0ea112ce3 100644 --- a/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events.md +++ b/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events.md @@ -147,7 +147,7 @@ Braze はセグメンテーション用として、これらのイベントが | ネストされたオブジェクト | 他のオブジェクトの中にあるオブジェクト。詳細については、この記事の「[階層化オブジェクト](#nested-objects)」のセクションを参照してください。 {: .reset-td-br-1 .reset-td-br-2} -配列またはオブジェクト値を含むイベントプロパティオブジェクトには、最大 50 KB のイベントプロパティペイロードを設定できます。 +配列またはオブジェクト値を含むイベントプロパティオブジェクトには、最大 100 KB のイベントプロパティペイロードを設定できます。 カスタムイベントプロパティのデータ型は変更できますが、データの収集後に[データ型を変更]({{site.baseurl}}/help/help_articles/data/change_custom_data_type/)した場合の影響に注意してください。 diff --git a/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md b/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md index c6e9574f496..9ad2a36882d 100644 --- a/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md +++ b/_lang/ja/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md @@ -15,7 +15,7 @@ description: "この記事では、階層化 JSON データをカスタムイベ ## 制限事項 - 階層化トされたデータは、[カスタムイベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/)と[購入イベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/)の両方でサポートされていますが、他のイベントタイプではサポートされていません。 -- 配列またはオブジェクト値を含むイベントプロパティオブジェクトは、最大 50 KB のイベントプロパティペイロードを持つことができます。 +- 配列またはオブジェクト値を含むイベントプロパティオブジェクトは、最大 100 KB のイベントプロパティペイロードを持つことができます。 - 購入イベントに対してイベントプロパティスキーマを生成することはできません。 - イベントプロパティスキーマは、過去 24 時間のカスタムイベントをサンプリングすることで生成されます。 @@ -172,7 +172,7 @@ description: "この記事では、階層化 JSON データをカスタムイベ ### 送信できる階層化データの量はどの程度ですか? -イベントの 1 つ以上のプロパティに階層化されたデータが含まれている場合、イベントのすべてのプロパティを合計した最大ペイロードは 50 KB です。そのサイズ制限を超えたリクエストは拒否されます。 +イベントの 1 つ以上のプロパティに階層化されたデータが含まれている場合、イベントのすべてのプロパティを合計した最大ペイロードは 100 KB です。そのサイズ制限を超えたリクエストは拒否されます。 [4]: {% image_buster /assets/img_archive/nested_event_properties_segmentation.png %} [5]: {% image_buster /assets/img_archive/nested_event_properties_personalization.png %} diff --git a/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md b/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md index 839848c15e0..bc8dbecb3a9 100644 --- a/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md +++ b/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md @@ -176,7 +176,7 @@ Braze には、ユーザーの LTV を把握するために参照できる主な {% tabs local %} {% tab キャンバスエントリのプロパティ %} -[キャンバスエントリのプロパティ]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)は、アクションベースまたは API でトリガーされるキャンバスにマップするプロパティです。`canvas_entry_properties` オブジェクトのサイズ上限は 50 KB であることに注意してください。 +[キャンバスエントリのプロパティ]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)は、アクションベースまたは API でトリガーされるキャンバスにマップするプロパティです。`canvas_entry_properties` オブジェクトのサイズ上限は 100 KB であることに注意してください。 {% alert important %} 特にアプリ内メッセージチャネルでは、以前の早期アクセスの一環として元のエディターで永続的なエントリプロパティを有効にしている場合、キャンバスフローと元のキャンバスエディターでのみ `canvas_entry_properties` を参照できます。 diff --git a/_lang/ko/_api/objects_filters/event_object.md b/_lang/ko/_api/objects_filters/event_object.md index 3eb55928183..43de0c2bd98 100644 --- a/_lang/ko/_api/objects_filters/event_object.md +++ b/_lang/ko/_api/objects_filters/event_object.md @@ -70,7 +70,7 @@ Braze에서 기존 고객 프로필만 업데이트하려면 요청 본문에 `t | 오브젝트 | 오브젝트가 문자열로 수집됩니다. | {: .reset-td-br-1 .reset-td-br-2} -배열 또는 개체 값을 포함하는 이벤트 속성 개체는 최대 50KB의 이벤트 속성 페이로드를 가질 수 있습니다. +배열 또는 개체 값을 포함하는 이벤트 속성 개체는 최대 100KB의 이벤트 속성 페이로드를 가질 수 있습니다. ### 이벤트 속성 지속성 이벤트 속성정보는 상위 이벤트에 의해 트리거된 메시지를 필터링하고 Liquid 개인화할 수 있도록 설계되었습니다. 기본적으로 이러한 정보는 Braze 사용자 프로필에 유지되지 않습니다. 세분화에서 이벤트 속성 값을 사용하려면 이벤트 속성 값을 장기 저장하는 다양한 접근 방식에 대해 자세히 설명하는 [커스텀 이벤트][5]를 참조하세요. diff --git a/_lang/ko/_api/objects_filters/purchase_object.md b/_lang/ko/_api/objects_filters/purchase_object.md index 674e2f4c322..bb96905451e 100644 --- a/_lang/ko/_api/objects_filters/purchase_object.md +++ b/_lang/ko/_api/objects_filters/purchase_object.md @@ -103,7 +103,7 @@ Authorization: Bearer YOUR-REST-API-KEY | 사물 | 개체는 문자열로 수집됩니다. | {: .reset-td-br-1 .reset-td-br-2} -배열 또는 객체 값을 포함하는 이벤트 속성 객체는 최대 50KB의 이벤트 속성 페이로드를 가질 수 있습니다. +배열 또는 객체 값을 포함하는 이벤트 속성 객체는 최대 100KB의 이벤트 속성 페이로드를 가질 수 있습니다. ### 구매 등록정보 diff --git a/assets/img_archive/canvas_exact_stats.png b/assets/img_archive/canvas_exact_stats.png new file mode 100644 index 00000000000..760cc45b524 Binary files /dev/null and b/assets/img_archive/canvas_exact_stats.png differ diff --git a/assets/img_archive/media_library_dalle.png b/assets/img_archive/media_library_dalle.png index 5c1bb765b7d..9c6516f8b04 100644 Binary files a/assets/img_archive/media_library_dalle.png and b/assets/img_archive/media_library_dalle.png differ diff --git a/assets/img_archive/multi_channel_footer.png b/assets/img_archive/multi_channel_footer.png index 0dd565812f9..d4421dd330c 100644 Binary files a/assets/img_archive/multi_channel_footer.png and b/assets/img_archive/multi_channel_footer.png differ diff --git a/assets/js/broken_redirect_list.js b/assets/js/broken_redirect_list.js index 844e8b4a588..97fd8ef9ed4 100644 --- a/assets/js/broken_redirect_list.js +++ b/assets/js/broken_redirect_list.js @@ -880,29 +880,29 @@ validurls['/docs/user_guide/sage_ai/generative_ai/ai_copywriting/'] = '/docs/use validurls['/docs/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/'] = '/docs/user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines/'; validurls['/docs/user_guide/sage_ai/generative_ai/ai_liquid/'] = '/docs/user_guide/brazeai/generative_ai/ai_liquid/'; validurls['/docs/user_guide/sage_ai/generative_ai/ai_content_qa/'] = '/docs/user_guide/brazeai/generative_ai/ai_content_qa/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_analytics/#churn_score'] = '/docs/user_guide/braze_ai/predictive_suite/predictive_churn/prediction_analytics/#churn_score'; +validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_analytics/#churn_score'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/#churn_score'; validurls['/user_guide/intelligence/faqs/#when-does-braze-check-the-eligibility-criteria-for-segment-and-audience-filters'] = '/user_guide/brazeai/intelligence/faqs/#when-does-braze-check-the-eligibility-criteria-for-segment-and-audience-filters'; validurls['/user_guide/intelligence/faqs/#why-is-re-eligibility-not-available-when-combined-with-intelligent-selection'] = '/user_guide/brazeai/intelligence/faqs/#why-is-re-eligibility-not-available-when-combined-with-intelligent-selection'; validurls['/user_guide/predictive_suite/predictive_churn/messaging_users/#filters'] = '/user_guide/brazeai/predictive_suite/predictive_churn/messaging_users/#filters'; validurls['/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/'] = '/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/'; -validurls['/docs/user_guide/predictive_suite'] = '/docs/user_guide/sage_ai/predictive_suite/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_churn/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_churn/creating_a_churn_prediction/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_analytics/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn/messaging_users/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_churn/messaging_users/'; -validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_faq/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_churn/prediction_faq/'; -validurls['/docs/user_guide/predictive_suite/predictive_purchases'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/'; -validurls['/docs/user_guide/predictive_suite/predictive_purchases/creating_a_purchase_prediction/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/creating_an_event_prediction/'; -validurls['/docs/user_guide/predictive_suite/predictive_purchases/prediction_analytics/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/prediction_analytics/'; -validurls['/docs/user_guide/predictive_suite/predictive_purchases/messaging_users/'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/messaging_users/'; -validurls['/docs/user_guide/intelligence'] = '/docs/user_guide/sage_ai/intelligence/'; -validurls['/docs/user_guide/intelligence/intelligent_channel/'] = '/docs/user_guide/sage_ai/intelligence/intelligent_channel/'; -validurls['/docs/user_guide/intelligence/intelligent_selection/'] = '/docs/user_guide/sage_ai/intelligence/intelligent_selection/'; -validurls['/docs/user_guide/intelligence/intelligent_timing/'] = '/docs/user_guide/sage_ai/intelligence/intelligent_timing/'; -validurls['/docs/user_guide/intelligence/ai_copywriting/'] = '/docs/user_guide/sage_ai/generative_ai/ai_copywriting/'; -validurls['/docs/user_guide/intelligence/faqs/'] = '/docs/user_guide/sage_ai/intelligence/faqs/'; +validurls['/docs/user_guide/predictive_suite'] = '/docs/user_guide/brazeai/predictive_suite/'; +validurls['/docs/user_guide/predictive_suite/predictive_churn'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/'; +validurls['/docs/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction/'; +validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_analytics/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/'; +validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/'; +validurls['/docs/user_guide/predictive_suite/predictive_churn/messaging_users/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/messaging_users/'; +validurls['/docs/user_guide/predictive_suite/predictive_churn/prediction_faq/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_churn/prediction_faq/'; +validurls['/docs/user_guide/predictive_suite/predictive_purchases'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/'; +validurls['/docs/user_guide/predictive_suite/predictive_purchases/creating_a_purchase_prediction/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction/'; +validurls['/docs/user_guide/predictive_suite/predictive_purchases/prediction_analytics/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/'; +validurls['/docs/user_guide/predictive_suite/predictive_purchases/messaging_users/'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/messaging_users/'; +validurls['/docs/user_guide/intelligence'] = '/docs/user_guide/brazeai/intelligence/'; +validurls['/docs/user_guide/intelligence/intelligent_channel/'] = '/docs/user_guide/brazeai/intelligence/intelligent_channel/'; +validurls['/docs/user_guide/intelligence/intelligent_selection/'] = '/docs/user_guide/brazeai/intelligence/intelligent_selection/'; +validurls['/docs/user_guide/intelligence/intelligent_timing/'] = '/docs/user_guide/brazeai/intelligence/intelligent_timing/'; +validurls['/docs/user_guide/intelligence/ai_copywriting/'] = '/docs/user_guide/brazeai/generative_ai/ai_copywriting/'; +validurls['/docs/user_guide/intelligence/faqs/'] = '/docs/user_guide/brazeai/intelligence/faqs/'; validurls['/docs/user_guide/intelligence/ai_content_qa'] = '/docs/user_guide/brazeai/generative_ai/ai_content_qa/'; validurls['/docs/user_guide/administrative/access_braze/resetting_your_password/'] = '/docs/user_guide/administrative/access_braze/accessing_your_account/'; validurls['/docs/user_guide/administrative/access_braze/getting_your_account/'] = '/docs/user_guide/administrative/access_braze/accessing_your_account/'; @@ -918,9 +918,9 @@ validurls['/docs/user_guide/data_and_analytics/custom_data/pre-populating_custom validurls['/docs/user_guide/data_and_analytics/custom_data/blocklist_delete_custom_data/'] = '/docs/user_guide/data_and_analytics/custom_data/managing_custom_data/#blocklisting-custom-data'; validurls['/docs/user_guide/data_and_analytics/configuring_reporting/'] = '/docs/user_guide/data_and_analytics/reporting/configuring_reporting/'; -validurls['/docs/user_guide/sage_ai/predictive_suite/predictive_purchases/creating_an_event_prediction'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/creating_an_event_prediction/'; -validurls['/docs/user_guide/sage_ai/predictive_suite/predictive_purchases/prediction_analytics'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/prediction_analytics/'; -validurls['/docs/user_guide/sage_ai/predictive_suite/predictive_purchases/messaging_users'] = '/docs/user_guide/sage_ai/predictive_suite/predictive_events/messaging_users/'; +validurls['/docs/user_guide/sage_ai/predictive_suite/predictive_purchases/creating_an_event_prediction'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction/'; +validurls['/docs/user_guide/sage_ai/predictive_suite/predictive_purchases/prediction_analytics'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/'; +validurls['/docs/user_guide/sage_ai/predictive_suite/predictive_purchases/messaging_users'] = '/docs/user_guide/brazeai/predictive_suite/predictive_events/messaging_users/'; validurls['/docs/copying_to_workspace'] = '/docs/copying_to_workspaces/'; validurls['/docs/developer_guide/platform_wide/feature_flags/use_cases/'] = '/docs/developer_guide/platform_wide/feature_flags/about/'; validurls['/docs/user_guide/message_building_by_channel/content_cards/customize/'] = '/docs/developer_guide/customization_guides/customization_overview'; @@ -930,8 +930,8 @@ validurls['/docs/partners/message_personalization/yotpo/'] = '/docs/partners/mes validurls['/docs/help/help_article/'] = '/docs/help/help_articles/'; validurls['/docs/user_guide/data_and_analytics/your_reports/viewing_and_understanding_segment_data/'] = '/docs/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/'; validurls['/docs/developer_guide/platform_integration_guides/fireos/push_notifications/integration/'] = '/docs/developer_guide/platform_integration_guides/android/push_notifications/fireos/integration/'; -validurls['/docs/user_guide/intelligence/intelligent_selection/'] = '/docs/user_guide/sage_ai/intelligence/intelligent_selection/'; -validurls['/docs/user_guide/intelligence/intelligent_timing/'] = '/docs/user_guide/sage_ai/intelligence/intelligent_timing/'; +validurls['/docs/user_guide/intelligence/intelligent_selection/'] = '/docs/user_guide/brazeai/intelligence/intelligent_selection/'; +validurls['/docs/user_guide/intelligence/intelligent_timing/'] = '/docs/user_guide/brazeai/intelligence/intelligent_timing/'; validurls['/docs/help/best_practices/email/overview/'] = '/docs/help/help_articles/email/'; validurls['/docs/user_guide/onboarding_with_braze/overview'] = '/docs/user_guide/getting_started'; validurls['/docs/api/objects_filters/user_attributes/object/'] = '/docs/api/objects_filters/user_attributes_object/'; @@ -1157,7 +1157,7 @@ validurls['/docs/user_guide/data_and_analytics/cloud_ingestion/file_integrations validurls['/docs/home/templates/tutorial'] = '/docs/contributing/templates/'; validurls['/docs/user_guide/data_and_analytics/your_reports/report_builder'] = '/docs/user_guide/data_and_analytics/reporting/report_builder/'; -validurls['/docs/recommendations'] = '/docs/user_guide/sage_ai/recommendations'; +validurls['/docs/recommendations'] = '/docs/user_guide/brazeai/recommendations'; validurls['/docs/SDK_Integration/Android'] = '/docs/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/'; validurls['/docs/api/endpoints/scim/post_update_existing_user_account'] = '/docs/api/endpoints/scim/put_update_existing_user_account/'; validurls['/docs/user_guide/message_building_by_channel/email/reporting'] = '/docs/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting/'; diff --git a/assets/js/developer_nav.js b/assets/js/developer_nav.js deleted file mode 100644 index a56f4fc2b78..00000000000 --- a/assets/js/developer_nav.js +++ /dev/null @@ -1,119 +0,0 @@ -$(document).ready(function () { - if (page_collection !== "developer_guide") { - return; - } - var exclusion_list = [ - "parent_nav_top_platformintegrationguides_sdkprimer", - "parent_nav_top_platformintegrationguides_sdkchangelogs", - ]; - - var url_selected = (location.pathname.split("/")[4] || "").replace(/_/g, ""); - if (site_language != 'en') { - url_selected = (location.pathname.split("/")[5] || "").replace(/_/g, ""); - } - var dev_selected = (url_selected - ? `parent_nav_top_platformintegrationguides_${url_selected}` - : Cookies.get("__dev_selected") || "").toLowerCase(); - var platform_objects = $("#nav_top_platformintegrationguides > div.nav-item"); - var platform_list = []; - var hide_list = []; - var show_list = []; - var select_html = - '
"; - $("#parent_nav_home div .nav_block").append(select_html); - $("#dev_select").change(function (e) { - var $this = $(this); - var cur_sel = $this.val(); - Cookies.set("__dev_selected", cur_sel); - if (!cur_sel) { - $(platform_list).each(function (i, v) { - $("#" + v).show(); - }); - } else { - $(platform_list).each(function (i, v) { - if (exclusion_list.indexOf(v) == -1) { - if ($("#" + v + " a").attr("aria-expanded") == "true") { - $("#" + v + " a").trigger("click"); - } - $("#" + v).hide(); - } - }); - show(cur_sel); - } - }); - $("#guide_featured_list a, #guide_list a").click(function (e) { - var $this = $(this); - var navlink = $this.attr("data-navlink"); - if (navlink) { - navlink = "parent_nav_top_platformintegrationguides_" + navlink; - if (platform_list.indexOf(navlink) > -1) { - Cookies.set("__dev_selected", navlink); - } - } - }); - - function hide(dropdown_id) { - var navigation_id = $("#" + dropdown_id + " a"); - $("#" + dropdown_id).hide(); - if (navigation_id.attr("aria-expanded") === "true") { - navigation_id.trigger("click"); - } - } - - function show(dropdown_id) { - var navigation_id = $("#" + dropdown_id + " a"); - $("#" + dropdown_id).show(); - if (navigation_id.attr("aria-expanded") === "false") { - navigation_id.trigger("click"); - } - } - -});