ÃÛ¶¹ÊÓƵ

To add an Content cards to a journey, follow these steps:

1. Open your journey, then drag and drop a Card activity from the Actions section of the palette.

   

2. Enter a Label and Description for your message.

3. Choose your Content card configuration to use.

   

4. You can now start designing your content with the Edit content button. Learn more

5. Enable the Enable additional delivery rules option. Then, Edit rules to choose the event(s) and criteria that will trigger your message. Rule builders enable users to specify criteria and values that, when met, trigger a set of actions.

   

   1. Click Add condition to select your event.

      accordion
      See available Event.
      table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 5-row-3 6-row-3 7-row-3 8-row-3 9-row-3 Package Trigger Definition Send data to Platform Sent data to Platform Triggered when the mobile app issues an edge experience event to send data to ÃÛ¶¹ÊÓƵ Experience Platform. Usually the API call from the AEP Edge extension. Core tracking Track action Triggered when the legacy functionality offered in mobile code API is called. Core tracking Track state Triggered when the legacy functionality offered in mobile code API is called. Core tracking Collect PII Triggered when the legacy functionality offered in mobile code API is called. Application lifecycle Application launch Triggered at every run, including crashes and installs. Also triggered on a resume from the background when the lifecycle session timeout has been exceeded. Application lifecycle Application install Triggered at the first run after installation or re-installation. Application lifecycle Application update Triggered at the first run after an upgrade or when the version number changes. Application lifecycle Application close Triggered when the application is closed. Application lifecycle Application crash Triggered when the application is not backgrounded before being closed. The event is sent when the application is started after the crash. ÃÛ¶¹ÊÓƵ Mobile crash reporting does not implement a global uncaught exception handler.

   2. Choose the Or condition if you want to add more Triggers to further expand your rule.

   3. Choose the And condition if you want to add Traits and better fine-tune your rule.

      accordion
      See available Traits.
      table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 5-row-3 6-row-3 7-row-3 8-row-3 9-row-3 10-row-3 11-row-3 12-row-3 13-row-3 14-row-3 Package Traits Definition Device info Carrier name Triggered when one of the Carrier name from the list is met. Device info Device name Triggered when one of the Device name is met. Device info Locale Triggered when one of the language from the list is met. Device info OS version Triggered when one of the specified OS version is met. Device info Previous OS version Triggered when one of the specified Previous OS version is met. Device info Run mode Triggered if Run mode is either application or extension. Application lifecycle App ID Triggered when the specified App ID is met. Application lifecycle Day of week Triggered when the specified day of week is met. Application lifecycle Day since first use Triggered when the specified number of day since first use is met. Application lifecycle Day since last use Triggered when the specified number of day since last use is met. Application lifecycle Day since upgrade Triggered when the specified number of day since last upgrade is met. Application lifecycle Install date Triggered when the specified Install date is met. Application lifecycle Launches Triggered when the specified number of Launches is met. Application lifecycle Time of day Triggered when the specified Time of day is met.

   4. Click Make group to group triggers together.

6. If necessary, complete your journey flow by dragging and dropping additional actions or events. Learn more

7. Once your Content card is ready, finalize the configuration and publish your journey to activate it.

For more information on how to configure a journey, refer to this page.

To start building your content cards through a campaign, follow the steps below.

1. Create a campaign. Learn more

2. Select the type of campaign that you want to execute

   • Scheduled - Marketing: execute the campaign immediately or on a specified date. Scheduled campaigns are aimed at sending marketing messages. They are configured and executed from the user interface.

   • API-triggered - Marketing/Transactional: execute the campaign using an API call. API-triggered campaigns are aimed at sending either marketing, or transactional messages, i.e. messages sent out following an action performed by an individual: password reset, cart purchase etc. Learn how to trigger a campaign using APIs

   

3. In the Properties section, specify a name and a description for the campaign.

4. In the Audience section, click the Select audience button to display the list of available ÃÛ¶¹ÊÓƵ Experience Platform audiences. Learn more on audiences

5. In the Identity namespace field, choose the namespace to use in order to identify the individuals from the selected segment. Learn more on namespaces

6. Select the Content card action.

   

7. Select or create a new Content card configuration.

8. To test the content of your message, click Create experiment. This allows you to test multiple variables of a delivery on sample populations to determine which treatment has the greatest impact on the targeted audience. Learn more about content experiment.

9. If additional triggers are required, use the Enable additional delivery rules toggle. Additional delivery rules are not required.

   Click Edit triggers to select the event(s) and criteria for message delivery. The rule builder lets you specify conditions and values that, when met, trigger actions.

   

10. You can schedule your campaign to a specific date or set to recur at regular intervals. Learn more

11. You can now start designing your content with the Edit content. Learn more