Step 4 of the wizard sends an experience to Adobe Target, AEM, Contentful or Tealium. This page covers each destination and what goes live.
Before you start #
Who can do this
Step 4 shows a card only for the destinations your organisation’s plan includes, and only the buttons your role allows. If you can’t activate, the wizard ends at step 3.
- Each destination uses your default integration for it: Adobe IO (with a tenant and a default workspace), AEM, Contentful or Tealium. Set the defaults as described in Edit, delete or set a default integration.
- Read Before you go live if this is your first activation.
Step 4: Activate the experience #
Step 4 opens when you click Save and Activate in the create wizard, or after you save and approve a version in the edit wizard. Each destination appears as a card. You can use more than one before you leave the page.
If the experience has never been approved, the first offer, entry or Tealium extension you create approves version 1 automatically.
Adobe Target #
To create a new offer:
- Click Create Offer.
- In Create Adobe Target Offer, enter the offer name and click Submit.
Stride creates a JSON offer (an HTML offer for templates that render HTML) in your default workspace, then shows the offer ID and workspace name.
To overwrite offers already linked to this experience, use Update Offer. It appears only when the experience is linked to an offer in your default Adobe IO integration.
- Click Update Offer.
- In Update Adobe Target Offer, choose one or more offers under Select Offer to Update and click Submit.
Changes live systems
A new offer isn’t live until someone uses it in a Target activity. Update Offer replaces the content of every offer you pick: if one is in a live activity, visitors see the change straight away.
AEM #
The AEM card appears only if your organisation has AEM, and only for templates of type No Preview whose source is API.
- Click Update AEM.
- Confirm in Update In AEM.
Stride writes the experience JSON into the AEM content fragment through your default AEM integration, replacing what was there.
Contentful #
- Click Create Entry.
- In Create Contentful Entry, choose a content type under Select Content Type to Create and click Submit. Only content types whose fields match the experience JSON are listed.
Stride creates the entry in your default Contentful space but doesn’t publish it. Publish it in Contentful when you’re ready. Entries you’ve already created are updated whenever the experience’s approved version changes.
Tealium Experience #
- Click Create Tealium Experience.
- In Create Tealium Entry, fill in the form:
| Field | What to enter |
|---|---|
| Enter name and Enter notes | Both required. The name becomes the extension name in Tealium iQ. |
| Scope | Before Load Rules, After Load Rules, DOM Ready, Tag Scoped Extensions or After Tag Extensions. |
| Occurrence | Run Once or Run Always (the default). |
| Targets | Tick QA, Dev and/or Prod. |
| Condition | Pick URL, an operator (equals, does not equal, contains, does not contain) and a value. Add Condition adds a rule to the group: all rules in a group must match. Add Group adds another group: any one group can match. |
- Click Create.
Changes live systems
Stride adds an active JavaScript Code extension to your default Tealium iQ profile and saves the profile, for the targets you ticked. Ticking Prod shows a warning: test on QA or Dev first.
After activation #
The new ID appears in the Activations column of Manage Experiences and under Available Activations on the experience details page, with a badge for the destination.
From then on, Stride keeps the activations in step with the approved version. Approving a new version, saving over the approved version or reverting updates every linked offer, entry and extension. See Edit, version, duplicate or delete an experience.
