API

This section is intended for developers utilizing our APIs to add channels.

Below you will find the keys to generate secret payloads for adding or updating a channel via the Script API.

Refer to the configuration page for detailed information on the purpose and usage of each input.

TWITTER_ACCESS_TOKEN

In this secret, you would store the OAuth token obtained from the Twitter OAuth process. oauth_token is the key name under which you get the value once Twitter OAuth is done. Example value 7588892-kagSNqWge8gB1WwE3plnFsJHAZVfxWD7Vb57p0b4 Type PASSWORD Optional false

TWITTER_ACCESS_TOKEN_SECRET

In this secret, you would store the access token secret that you got back from the Twitter OAuth process. oauth_token_secret is the key name under which you get the value once Twitter OAuth is done. Example value PbKfYqSryyeKDWz4ebtY3o5ogNLG11WJuZBc9fQrQo Type PASSWORD Optional false

TWITTER_PIXEL_ID

Use for storing the Pixel ID.

Example value qczn8 Type IDENTIFIER Optional false

TWITTER_ACCOUNT_ID

Use for storing Ad Account ID

Example value 18ce55iyn1h Type TEXT Optional false

TWITTER_BROWSER_PIXEL

See the config description.

Possible values 1 or 0

Type CHECKBOX

Optional true

TWITTER_CONVERSIONS

In this secret, we would need a stringified data array mapping between Twitter events and EdgeTag events. Each item in the array would be an object with a label key containing the Twitter event ID, and an event key containing the EdgeTag event name.

Example value

[{"label":"qczne","event":"PageView"},{"label":"qczos","event":"AddToCart"}]

See the config description.

Type TEXT

Optional false