Targeting Platform

Prerequsites

To use module following tools need to be configured:

• Redis - is used for caching platform information (catalog of lineitems/adgroups e.g.) and locks. It depends on amount of information in your platform but as a starting point 1Gb memory will be enough. For now only single entrypoint is supported. Prefix for cache keys is PLATFORM_CACHE_ (set in CACHE_KEYS_PREFIX) and for locks PLATFORM_LOCK_ (LOCK_KEYS_PREFIX).

Credentials for platforms

Each platform has it's own format of credentials. You need to obtaint credetantial before starting to use platforms thorugh this module.

DV360 (dv360)

Requires service account private key (whole JSON for service account). E.g.

{
    "type": "service_account",
    "project_id": "",
    "private_key_id": "",
    "private_key": "-----BEGIN PRIVATE KEY-----\n\n-----END PRIVATE KEY-----\n",
    "client_email": "",
    "client_id": "",
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://oauth2.googleapis.com/token",
    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
    "client_x509_cert_url": ""
}

Meta (Facebook) (meta)

Example of credentails (app_scoped_system_user_id is required for detailed access validation):

{
    "access_token": "",
    "app_scoped_system_user_id":
}

The Trade Desk (ttd)

Example of credentials (login and password is required for automatic token renewal):

{
    "PartnerId": "",
    "token": "",
    "Login": "",
    "Password": ""
}

Platforms

DV360

Library works as with normal lineitems as with YouTube through SDF. In case of passing lineitem id for YouTube (in array all ids should be either for normal or YouTube lineitems) methods will return Pandas DataFrame with prepared data - you need to get CSV from it and manually upload to Google.

Meta

While testing/using you can receive Rate Limit (set by Meta Marketing API) - you need to monitor your limits before operations. For current implementaion (probably will be chnaged in future releases) there is no retries and exceptions - you simply get empty result (means set/chnaged nothing).

The Trade Desk (TTD)

Setting locations (geofence) in Data Groups can take a time - about 45 minutes. It is how TTD operates - it takes seconds to create thousands of points in geofences, but about an hour while they will be availible to use (TTD API). In code we have expponential retries to repeat operations till success (do not be confused - 403 error does aslo mean "we can't find geofence" in terms of TTD) - so all you need to wait.

How to use

See examples in integration tests.

You can adopt these tests by placing appropriate sectet files into folder secrets.

Locks

To prevent simultanous updating of the same placements in the platform locks are used. While you are calling clear, pause, delete and set operations lock will be acquired and released in the end of the operation (or after 1 hour in case of any error). If method can't acquire lock it will return empty results (no exception raised).