Last updated 2024年9月27日

Census

Census is a customer data platform that enables clients to easily send data to third-party platforms through data integrations. With Census’s existing Rokt Destination, users can effortlessly send conversion data from their Census account to Rokt, enabling more precise targeting, better personalization, and improved campaign outcomes.

This guide outlines the steps required to set up your Rokt integration within Census to easily send comprehensive and enriched conversion data to Rokt to connect marketing activity, such as a Referral, to outcomes that drive business value, such as a customer Conversion (e.g., purchases, subscriptions, or application downloads). This includes required steps for authentication as well as an example implementation using HTTP.

Integration Setup

Authentication

Authenticating with the Rokt Events Connector requires an AppId, AppSecret and Account ID. Read Generating AppId & AppSecret for more information.

Creating a Rokt Destination

1. Login to your Census account

2. Click on Destinations on the left navigation bar and click New Destination

   

3. Search for the Rokt Destination

   

4. Add the Account ID you want to send conversions to using your AppId and AppSecret

• Do not Add API Key

5. Click Login to create an OAuth2 connection between Census and Rokt

6. Click Connect to run the connection verification step

   

7. A successful connection will look like this:

   

8. Click Test to create a Healthy destination connection

   

9. If the connection succeeds, you will see Rokt Destination as Healthy

   

Creating a Sync

The most important component in your Census integration is defining a Sync. A Sync defines the rules of how data should be synced, from your selected Data Source to your Destination. For detailed documentation on Syncs, refer to the Census Sync Overview.

1. Click on Syncs and then click + Create a sync

   

2. Select your desired Data Connection & Source. For Destination, set Connection to Rokt and Object to Event. Ensure that the Sync Behavior is set to Send and set your desired Sync Key.

   

3. Add Rokt Field Mappings

To ensure conversions and associated metadata is sent to Rokt in the correct format, the following elements must be captured and ultimately received by Rokt:

Parameter	Description	Required / Recommeneded
Event Type	Type of Event or Action	Required
Event ID	An identifier used to uniquely identify an event	Required
Event Time	Time of the event in UTC	Required
Email	Email passed as plain text, lowercase and without trailing spaces	One email field is necessary. Raw is preferred but hashed is acceptable. Raw and hashed is recommended.
Email (already SHA256 hashed)	SHA-256 hash of email address, already hashed	See Above
Email (apply SHA256 hash)	SHA-256 hash of email address. Tealium will hash	See Above
Rokt Tracking ID	A Rokt-generated ID used to match conversion events to the originating click	Recommended
Mobile	Mobile phone number of converting customer	Recommended
First Name	Customer's first name	Recommended
Last Name	Customer's last name	Recommended

注記

For a full list of supported parameters, refer to the Event API documentation. We recommend you include fields like transaction amount, currency code, product details, and payment method to provide context for better targeting and optimizations.

4. Click Run Test. A successful test will show Sync test succeeded along with checks for Fetching a record from data source and Loading into Rokt

   

5. The Show API Inspector will show the status code and response from the Rokt Event API. This is a tool that can be used to understand why the test failed. Success will return an HTTP status code 200.

You are now finished! For questions and concerns, please reach out to your Rokt contact or account manager.