Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

List of Channels

List of names of traffic sources you work with.

Next to each name is some basic info and the (far right side) option to edit/duplicate/archive this source.

Add/Edit Channel

Channel Name

Choose the mandatory name for this channel. Note it gets auto-saved when the field loses focus or when you click Enter.

Waterfall

The list of Ad Sources connected to this supply source. Meaning the ad sources that can get traffic from this traffic source.

Configuration

Optional advanced settings.

Please remember to click Save after you’re done.

  1. Optimized - each priority can have many ad sources. We recommend enabling this option to let our intelligent algorithm determine which ad sources should get more chances to win inside each given priority.

  2. Enable ads.txt - enable in order to apply https://aniview-test.atlassian.net/wiki/spaces/BASIC/pages/33036/Advertisers#ads.txt settings.

  3. Channel Type - normally Client, but some traffic sources (such as apps) may require you to choose Server instead. Prebid is reserved for future use.

  4. TimeoutMs - you can type the number of MS instead of relying on automation.

  5. Channel Cost - you can switch between Fixed CPM (a fixed amount of money for every 1,000 impressions) and Rev Share (where your publisher gets this revenue share).

  6. Limit Advertiser - only allow specific advertisers to be connected to this waterfall.

  7. Floor Price - don’t send requests for ad sources that ask for less than this amount.
    Only used for direct traffic that isn’t associated with specific publishers!

  8. Environment - choose where the traffic source is expected to run (Desktop, CTV, etc.). Note it’s used for reporting only.

  9. Override Publisher Supply Chain - use an alternative supply chain (as determined by the connected App/Site, to be used for regular connections.

  10. Override Partner Supply Chain - use an alternative supply chain (as determined by the connected App/Site, to be used for direct connections (aka deal IDs).

  11. App/Site - the alternative supply chain definition used for either or both Override Publisher Supply Chain and Override Partner Supply Chain.

  12. Seller ID (read-only) - the publisher ID used for App/Site.

Verified Sources

Also known as “First Look”, these ad sources will always be given a chance to compete for the auction and bypass automated optimization. Of course, they’ll still respect any targeting they might have.

Priority 1-3

Each priority can have many ad sources that will be used according to the Optimization (if it’s enabled) and respect any targeting they might have.

Priority 3 will only be used after Priority 2 and so on.

Trackers

Optionally apply a pixel for certain metrics, thus getting a report every time this pixel was used.

You will need to provide your tracking URL, mention its usage method, and use any macro we have to offer (e.g., https://your-tracker.com/?url=[AV_URL]&OS=[AV_OS] will track which exact URL and Operating System ads were displayed at). You can also control if you like to apply this tracker all the time or just some of the time.

You may use as many trackers as you like.

Player Settings

Partner Connections

Optionally connect this channel to a direct connection (aka Deal ID).

Add/Edit Partner Connection

When you click to add a new connection or click to edit an existing one, you are presented with many useful options, most of which are optional!

Please remember to click Save after you’re done.

Basic Info
General
  1. Name (required) - the name of the connection. It can be identical to the channel in order to avoid confusion.

  2. Description -any note you like to add about this connection.

  3. Status - remember to switch to Active, or this connection won’t be used.

  4. Demand Publisher - choose to link this connection to one of the Advertisers.

  5. Environment - choose where the connection is expected to run (Desktop, CTV, etc.). Note it’s used for reporting only.

  6. Partner ID - choose which of the Partners to use.

Business Model
  1. Floor Price (required) - the number of minimal revenues this connection expects from its Ad Sources, whereas anything less will be automatically blocked.

  2. Paying Method - you can switch between Fixed CPM (a fixed amount of money for every 1,000 impressions) and Rev Share (where your partner gets this revenue share).

  3. Fixed CPM or Rev Share - how much to pay for Fixed CPM or how much percent to pay for Rev Share.

Payments Model

The default revenue measurement is by impression (aka CPM). You can choose alternative revenue measurements (such as getting paid for clicks).

Impression Capping

Optionally limit how many impressions can be generated by this source.

This can be useful in direct deals when your advertiser limits you in advance on money terms.

Requests Per Day

Optionally limit how many requests can be generated by this source.

This can be useful in cases when your advertiser gives you a fee for sending too many requests (or at least for requests that don’t become impressions).

Frequency Capping

Optionally limit how many unique impressions can be generated by this partner.

This can be useful in direct deals when your advertiser limits you in advance on money terms.

Targeting

Optionally prevent requests for traffic that doesn’t meet certain requirements.

For example, if you exclude this-site.com, it will make sure no requests are sent from it to everything that uses this targeting.

Many types of targeting are available, even advanced ones such as IP addresses and User Agents.

  1. Domains

    Include/exclude only specific domains and/or sub-domains. You could type a domain or choose from a list.
    Empty Domains/Bundles (which are usually undesired by premium Advertisers) can also be controlled from the account’s global https://aniviewwiki.atlassian.net/wiki/spaces/HELP/pages/2280489267/Core+Settings#Domain .

  2. OS

    Include/Exclude specific operating systems (which can also be used as Environment - for example, include just Desktop traffic by choosing just Desktop OSs).

  3. Player Size

    Include/Exclude only specific player sizes. Note you can also choose Custom to define ranges of sizes (click Plus to add more ranges).

  4. Slot Type

    Include/Exclude just Preroll (ads that are shown before a video starts), Midroll (ads that are shown during a video) and/or First in Session.

  5. Hour of day

    Include/Exclude only traffic that arrives during specific days and/or hours

  6. User/Consent

    Include/Exclude traffic that may attract complaints or even blockage from premium Advertisers:

    1. Empty AD_IDFA - applications that don’t pass advertising ID (note it’s often blocked in iOS).

    2. Empty GDPR Consent in EU - EU sites that don’t even ask the user for to accept/reject tracking.

    3. Empty CCPA in California - when users in California aren’t offered a way to reject tracking.

    4. Empty Buyer UID in RTB (Cookie Sync Miss) - when Buyer ID is missing for some reason.

    5. Bots - when the traffic appears as non human.

  7. ads.txt

    Include/Exclude traffic that arrives only from certain Publishers.

  8. Placement Type

    Include/Exclude traffic from only specific types of Player Tags:

    1. In-Stream - players that have video content in which the ads appear before/during/after.

    2. In-Banner - players that usually appear in right/left side of webpages in a fixed location and size (usually 300x250).

    3. In-Article - player that appear between paragraphs.

    4. In-Feed - similar to In-Article.

    5. Floating or Sticky - all types of players even when they float (when the user scrolls away from them) or are always stick to the corner of webpages.

  9. Custom Targeting

    Include/Exclude every type of traffic that is supported by https://aniviewwiki.atlassian.net/wiki/spaces/BASIC/pages/152993816/Macros.
    Note you can’t type values directly, but only choose from lists which you can create and edit.

IVT

Optionally enable specific fraud detection and/or prevention.

Keep in mind it might already be enabled in the account level.

Publisher Connections

Optionally connect this channel to a regular connection.

This is where you can determine which publisher owns this website/app and thus give it proper dashboard access.

Add/Edit Publisher Connection

When you click to add a new connection or click to edit an existing one, you are presented with many useful options, most of which optional!

Please remember to click Save + Channel after you’re done. This will also create a channel inside the publisher’s login, which is needed for the process.

You can optionally click just Save, but this means you’ll have to log in into the publisher and manually create a connection there.

Basic Info
General
  1. Name (required) - the name of the connection. It can be identical to the channel in order to avoid confusion.

  2. Description -any note you like to add about this connection.

  3. Status - remember to switch to Active or this connection won’t be used.

  4. Demand Publisher - choose to link this connection also to one of the Advertisers.

  5. Environment - choose where the connection is expected to run (Desktop, CTV, etc.). Note it’s used for reporting only.

  6. Publisher ID - choose which of the Publishers to use.

Business Model
  1. Floor Price (required) - the amount of minimal revenues this connection expects from its Ad Sources, whereas anything less will be automatically blocked.

  2. Paying Method - you can switch between Fixed CPM (a fixed amount of money for each 1,000 impressions) and Rev Share (in which your publisher gets this share of the revenue).

  3. Fixed CPM or Rev Share - how much to pay for Fixed CPM or how much percent to pay for Rev Share.

Payments Model

The default revenue measurement is by impression (aka CPM). You can choose alternative revenue measurements (such as getting paid for clicks).

Impression Capping

Optionally limit how many impressions can be generated by this source.

This can be useful in direct deals when your advertiser limits you in advance on money terms.

Requests Per Day

Optionally limit how many requests can be generated by this source.

This can be useful in cases when your advertiser gives you a fee for sending too many requests (or at least for requests that don’t become impressions).

Flight Settings

Optionally choose dates when you automatically start and and end this source.

Targeting

Optionally prevent requests for traffic that doesn’t meet certain requirements.

For example, if you exclude this-site.com, it will make sure no requests are sent from it to everything that uses this targeting.

Many types of targeting are available, even advanced ones such as IP addresses and User Agents.

  1. Domains

    Include/exclude only specific domains and/or sub-domains. You could type a domain or choose from a list.
    Empty Domains/Bundles (which are usually undesired by premium Advertisers) can also be controlled from the account’s global https://aniviewwiki.atlassian.net/wiki/spaces/HELP/pages/2280489267/Core+Settings#Domain .

  2. OS

    Include/Exclude specific operating systems (which can also be used as Environment - for example, include just Desktop traffic by choosing just Desktop OSs).

  3. Player Size

    Include/Exclude only specific player sizes. Note you can also choose Custom to define ranges of sizes (click Plus to add more ranges).

  4. Slot Type

    Include/Exclude just Preroll (ads that are shown before a video starts), Midroll (ads that are shown during a video) and/or First in Session.

  5. Hour of day

    Include/Exclude only traffic that arrives during specific days and/or hours

  6. User/Consent

    Include/Exclude traffic that may attract complaints or even blockage from premium Advertisers:

    1. Empty AD_IDFA - applications that don’t pass advertising ID (note it’s often blocked in iOS).

    2. Empty GDPR Consent in EU - EU sites that don’t even ask the user for to accept/reject tracking.

    3. Empty CCPA in California - when users in California aren’t offered a way to reject tracking.

    4. Empty Buyer UID in RTB (Cookie Sync Miss) - when Buyer ID is missing for some reason.

    5. Bots - when the traffic appears as non human.

  7. ads.txt

    Include/Exclude traffic that arrives only from certain Publishers.

  8. Placement Type

    Include/Exclude traffic from only specific types of Player Tags:

    1. In-Stream - players that have video content in which the ads appear before/during/after.

    2. In-Banner - players that usually appear in right/left side of webpages in a fixed location and size (usually 300x250).

    3. In-Article - player that appear between paragraphs.

    4. In-Feed - similar to In-Article.

    5. Floating or Sticky - all types of players even when they float (when the user scrolls away from them) or are always stick to the corner of webpages.

  9. Custom Targeting

    Include/Exclude every type of traffic that is supported by https://aniviewwiki.atlassian.net/wiki/spaces/BASIC/pages/152993816/Macros.
    Note you can’t type values directly, but only choose from lists which you can create and edit.

Audit

(Read-only) Keeps constant track of who modified the channel, what was changed and when.

Great for troubleshooting!

  • No labels