Adobe Target
Use GrowthLoop audiences for Adobe Target visitor profile personalization.
Connect this destination to export audience membership as visitor profile attributes, for use in Adobe Target personalization.
This destination writes to your Adobe Target account and is a good fit when you want to:
- Use GrowthLoop audiences available as Target profile attributes
- Match visitors with a third-party ID or Target PCID
This maps to GrowthLoop Audiences and Journeys:
| Use it for | Audiences | Journeys |
|---|---|---|
| Writing audience membership onto Adobe Target visitor profiles | ✓ | ✓ |
GrowthLoop does not create a named Target audience. If you need a named AEP audience, use Adobe Experience Platform.
Prerequisites
Make sure you have:
- An active Adobe Target account with profile API access.
- A project in the Adobe Developer Console with the Adobe Target API added. You need Developer access to retrieve the Client ID and Client Secret. See Adobe's create a project guide.
- Your Adobe Target Client Code and Tenant Name.
Set up Adobe Target as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Click New Destination on the upper right side.
- Search for Adobe Target and click Add Adobe Target.
NoteDon't see Adobe Target when you try to add a destination? Reach out to [email protected] and we'll enable it.
- Enter the required information, then click Create.
| Field | Description |
|---|---|
| Destination Name | Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Adobe Target Personalization". |
| Sync Frequency | Set the default export frequency (for example, daily or weekly). You can override this setting for individual exports. |
| Client Code | Your Adobe Target client code. GrowthLoop uses it when uploading profile data. |
| Tenant Name | Your Adobe Experience Cloud tenant name. |
| Client ID | API key from your Adobe Developer Console project. |
| Client Secret | Client secret from the same project. |
GrowthLoop validates the credentials. Adobe Target then appears in your list of connected destinations.
Export to Adobe Target
From within GrowthLoop, export from an audience or from a journey Destination Node. See Export an audience or Build a journey if you need more information on these steps.
After building or selecting an audience, click Export, then search for Adobe Target. In a journey, add a Destination Node under Ads and select Adobe Target.
Map identifiers
Map the identifier that matches how visitors are identified on your site or app.
| Match field | Description |
|---|---|
| Third Party ID | Your company's visitor ID. Use this when you pass mbox3rdPartyId (or similar) to Target. |
| First Party Visitor ID (PCID) | The visitor ID Adobe Target generates. |
For live personalization, the ID you export must match the ID passed to Target on the site. You can also map custom attributes from the audience or from the journey as additional fields.
Configure the export
This is where you set the campaign type and schedule for audience exports. On a journey Destination Node, you set timing on the journey canvas.
| Setting | Audience export | Journey Destination Node |
|---|---|---|
| Export Name | Defaults to the audience name. | Required. Enter a name so you can find the export in GrowthLoop. |
| Campaign type | Choose a one-time or ongoing export. | The journey schedule controls when the journey runs and contacts are sent to Adobe Target. |
| Export Inclusion Criteria | Choose All audience members or Newly added audience members. | The journey sends contacts who reach the Destination Node. |
| Schedule | Set frequency, start date, end date, and days of the week. | Users reach this node when the journey runs. Add a Delay Node or set Criteria Evaluation to control timing. |
| Additional Fields | Optional. Map extra profile attributes for personalization in Target. | Optional. Map extra profile attributes for personalization in Target. |
Export behavior
This is what GrowthLoop writes when you export an audience.
| Behavior | What happens |
|---|---|
| What GrowthLoop writes | Visitor profile attributes. Direction is GrowthLoop → Adobe Target. |
| When it runs | GrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. Journeys send exports on demand when users reach the Destination Node. |
| Upload | GrowthLoop exports a CSV and uploads profile attributes with Adobe's Bulk Profile Update API. |
| Named audiences | GrowthLoop does not create a named Target audience. Attributes land on each visitor profile. |
| Personalization | Additional fields are supported. |
| UI delay | Bulk-uploaded attributes may not appear in the Target audience builder until Target observes the attribute on a site visit or through an active profile script. |
| One-time exports | GrowthLoop writes current membership attributes once. |
| Ongoing exports | GrowthLoop writes updated profile attributes on each scheduled run. |
Confirm the export was successful
When the run finishes, confirm you can use the data in Adobe Target.
- Audience export: Look up a visitor profile and confirm the exported attributes.
- Journey Destination Node: Look up a visitor who reached the node and confirm the exported attributes.
To confirm a specific profile received the data, use Adobe Target's Profile Fetch API in your sandbox or with your Adobe administrator.
In GrowthLoop, review counts on the audience Exports tab, or open the Activity tab on the journey Destination Node. See Export an audience or Monitor a journey for more information.
Congrats on successfully exporting to Adobe Target!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| Connection fails to validate | The Developer Console project does not include the Adobe Target API | Confirm the project includes the Adobe Target API |
| Profiles do not update | The mapped ID does not match how visitors are identified on the site | Map Third Party ID if you identify visitors with your own customer ID. Map PCID if you rely on Target's first-party cookie |
| An attribute is missing in the Target audience builder | Target has not observed the attribute yet | Wait for a site visit or profile script to surface it |
Updated 8 days ago