Demand Partners
If you are a DSP or demand partner and you would like to connect with Triplelift, there are a few things that we either require or highly recommend:
Testing your integration
We have a full sandbox environment that can simulate both real-time and API calls. To test your integration, ask your TripleLift contact for credentials.
Setting up User Sync
TripleLift can store the mappings of your user IDs, which will be sent in the bid response. You may also store the mappings. The following are the scenarios for initiating and storing user ID mappings:
| Usersync Initiator | Usersync stored by | Details | Implementation |
|---|---|---|---|
| TripleLift | TripleLift | TripleLift initiates the pixel call on an impression with one of our partner sites, the request will hit your usersync endpoint. If you know the user, you redirect back to us with your user ID. If you don't know the user, you simply return the pixel. | Using the production DSP UI, you would add a pixel endpoint that points to an endpoint on your system. This redirects to the xuid endpoint. |
| TripleLift | Partner | TripleLift initiates the pixel call on an impression with one of our partner sites, the request hits the TripleLift /getuid endpoint. This will redirect to your designated endpoint with the $UID field populated by our server. | Using the production DSP UI, you would add a pixel endpoint that points to the TripleLift /getuid endpoint, with the redirect populated to hit your endpoint and store the replaced $UID field as the TripleLift ID. |
| Partner | TripleLift | You either 1) drop a pixel that points directly to the TripleLift endpoint with your user ID populated, as required in the /xuid call, or 2) make a call to your server and redirect to the /xuid call with the ID populated. | This is setup and managed entirely by you. |
| Partner | Partner | You drop a pixel that points directly to the TripleLift /getuid endpoint, with a redirect pointing to your endpoint. | This is setup and managed entirely by you. |
For more details on the endpoints, please see Usersync.
Datacenters
The following are the various locations of our data centers:
| Region | Location | AWS Region |
|---|---|---|
| US East | Northern Virginia | us-east-1 |
| US West | Northern California | us-west-1 |
| Europe | Frankfurt | eu-central-1 |
| Asia South | Singapore | ap-southeast-1 |
Creative Approval
When a bid is submitted, all the assets are validated. New assets must go through our creative approval process, which consists of the aspects described below. The bid automatically enters the assets into the approval process (if they're not already approved). There is no fee for creative approval, and it will generally complete within business 24 hours.
- Image Approval: Each image must be validated both by an automated system and a human. Humans will block low-quality or profane images from the platform, and may reject those that are otherwise unfit for advertising.
- Logo Approval: Logos are not required in the bid, but when they are provided they must be approved. Generally, the same standards used for image approval will be used for logo approval.
- Brand Approval: The brand specified in the bid response is used for category-level and brand-level allow-lists and block-lists. Therefore, we must categorize every new brand that comes into the system. If you bid with a brand (or a phrasing of a brand) that we haven't seen, a human will automatically categorize and approve the brand.
Updated over 1 year ago