Use External Dynamic Naming Convention Parameters
Updated
While creating an ad entity, you can build a naming convention that includes a field that lives outside the Sprinklr platform. In order to achieve this capability, we create a custom field at the campaign, ad set, and ad variant levels that will be filled from an external source.
To explore this capability, please work with your Success Manager. |
Note External Dynamic Naming Convention will only work with published ad entities. |
Before You Begin
Familiarize yourself with how to create an External Custom Field.
How it Works in Sprinklr
You will need to provide a list(s) of unique names that you want to use for your campaign/ad set/ad in a doc file. We use this doc as a repository of available unique names that is used whenever a new campaign/ad set/ad is created.
Custom fields for Campaign Code, Ad Set, and Ad Code will be created and configured within the Campaign, Ad Set, Ad naming convention macros in the environment.
When a new Campaign/Ad Set/Ad is created, Sprinklr picks a unique name from the repository and inserts it into the respective field.
Then, we remove the code from the repository so it does not get reused.
To ensure the uniqueness of the ad entity names, we constantly monitor the provided repository and removes the used parameters.
Sprinklr monitors the repository and sends an email alert when it’s running low.
Examples of External Dynamic Naming Convention
Example: Campaign Code Specification | Example: Ad Set Code Specification |
|
|