StackAdapt Reference

Destination Info

Client-side
Server-side

Web

Mobile

Server

Retargeting

StackAdapt has extensive support for crafting audiences to retarget. By sending retargeting events to StackAdapt, you can craft campaigns to focus on audiences you know are already interested.

Retargeting Audience events require a retargeting_id in the same way Conversion Events require a conversion_id. The process to set up these events is the same. Following along with the conversion events guide above, we can create a Transformation that sends a constant property (retargeting_id) with the retargeting audience unique ID as the value.

Example:

Server-side

You may provide the following additional event properties when sending events to StackAdapt via Freshpaint's servers:

Event property

Type

Required?

Description

$sapid

string

Required for Click-Through Conversion Events

sapid is generated at ad click time and appended to the landing page URL. Freshpaint will automatically capture sapid for events from your website. For events from other sources you would need to provide $sapid.

conversion_id

string

Required for Conversion Events

conversion_id maps to a Conversion Event in StackAdapt. This uniquely describes the conversion event taking place.

retargeting_id

string

Required for Retargeting Events

retargeting_id maps to a Retargeting Audience in StackAdapt. This directly places the user in that Audience.

$ip

string

Required for Retargeting Events and View-Through Conversion Events

Non-hashed public IP address of the browser

$user_agent

string

Required for Retargeting Events

User agent from the user’s device

Considerations

  • Conversions may take up to 2 hours to appear in your StackAdapt portal.

Last updated

Was this helpful?