What this is
Smadex is a batch destination: data flows out of Zeotap CDP to Smadex, never the other way. Zeotap uploads audience segments to Smadex using the Smadex API, sending CSV files containing user data, so your audiences become targetable in your Smadex campaigns without manual exports or file transfers. Smadex is a mobile-first programmatic demand-side platform (DSP) for user acquisition, retargeting and branding campaigns. Because this is a batch destination, you attach it to an audience, not to a journey. Smadex sits under Batch Integrations in the Destinations catalogue, and Zeotap CDP does not list Smadex among its sources — so this page covers the outbound direction only.Supported identifiers and actions
Smadex supports the following ID types:
The integration exposes a single action: Smadex Audience Upload.
Note:Smadex accepts a single ID type per audience. Select the ID type under Additional Settings that corresponds to the identifier you map, and ensure it matches how your Smadex campaigns are configured. You cannot activate the same audience using a different identifier. In Smadex, uploaded audiences appear under the tab matching their ID type (Device ID, IP or IDFV).
Prerequisites
Before you create a Smadex destination in Zeotap CDP, make sure you have:- An active Smadex account with access to the Smadex platform (
hub.smadex.com). - A Smadex API Key, used for Smadex API authentication. If you are unsure where to find your API Key, contact your Smadex account representative.
- A Catalogue attribute that holds the identifier you intend to send, so it is available to map.
- The upstream setup covered in the Destinations prerequisites.
Create the Smadex destination
1
In the Zeotap CDP app, go to Integrate > Destinations.
2
Click + Create Destination.
3
Under All Destinations, search for Smadex and click the Smadex card (Upload audience segments to Smadex).

4
On the Enter Destination Details screen, enter the required details:a. Under Destination Name, enter a name for the destination.b. Under Smadex API Key, enter your Smadex API Key.
c. Review the values and click Next to move to the Mapping step.

5
On the Mapping step, under Choose your Action, select Smadex Audience Upload.

6
Under Map the Fields, map the Catalogue attribute that holds your identifier (for example, Maid) to the Identifier destination field.Then, under Additional Settings, select the ID type that corresponds to the mapped identifier from the supported identifiers above.

7
Click Create Destination. A confirmation message appears and the new destination is listed on the Active Destinations tab of the Destinations page, ready to be linked to an audience.

Link an audience to the destination
Note:The terms Audiences and Segments are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an Audience or a segment could be a specific group of customers who are over 18 years of age and who have performed an
addToCart event within the last 30 days.


Note:Every push delivers a full refresh of the audience to Smadex; incremental (delta) uploads are not sent.
Verify the audience reached Smadex
In Zeotap CDP, the audience row on the Batch tab of the Audiences list carries an Audience Status and an Activation Status; see Audience Status and Activation Status for what each value means. Once the audience is activated and the data is delivered, verify it in Smadex:1
Log into your Smadex account and go to Audiences > My Audiences.
2
On the My Audiences list page, find the audience sent from Zeotap. Audiences are grouped under the tab that matches their ID type (Device ID, IP or IDFV), and the list shows the audience ID, name, number of Active files, Type and Dev ID Type (Raw or Hashed), along with the created and updated dates.

3
Open the audience to review its details and upload activity. The uploaded files sent by Zeotap are listed with names in the 
Zeotap_<audience_id>_<timestamp>.csv format, along with the Status of each file.
Note:When a new file is uploaded, Smadex automatically removes the older files of the audience. This keeps the audience data fresh and prevents an incorrect audience count, so files showing a DELETED status after a new upload are expected and not an error.