Support & FAQs

How can we help?

Pixalate’s Ad Trust & Safety API Suite is trusted by industry leaders to protect their traffic against ad fraud and you can get started with just a few lines of code. Visit our help docs to learn more about using Pixalate’s Ad Trust & Safety API Suite.

Getting Started

Start here and begin using Pixalate’s Ad Trust & Safety API Suite.

Get Started »

Using the APIs

Get technical details on how to implement Pixalate’s Ad Trust & Safety API Suite.

Get Details »

Can’t find what you’re looking for?

Our team is available to answer questions you may have about using Pixalate services.

File a ticket by form

Open a ticket with all the relevant information.

Contact Us »

Test the API

Test the API with the API Explorer.

Test the API »

Schedule a demo

Interested in other Pixalate services? Reach out and we would be happy to show you around.

Schedule Demo »

Frequently Asked Questions

How do I get started using the Pixalate Ad Trust and Safety APIs?

Visit our “Getting Started” page for information on how to begin using the Pixalate Ad Trust and Safety API suite. If you need further assistance, our team is ready to help so please visit our support page for information on how to contact us.

Getting Started »

When registering, do you allow a personal email address to sign up?

At this time, we require a business email address to register for a free Pixalate account.

Register For Free »

Do I need a login to access the Pixalate APIs?

Yes, an account is required to login and use the Pixalate Ad Trust and Safety API suite, and to access your API key. Our “Getting Started” page can provide more information on how to create your free account.

Getting Started »

Are there other login options available aside from creating a username and password?

Our authentication system allows you to login using your Google or LinkedIn account.

Register For Free »

Do you have any strong password requirements?

Yes, we enforce strong passwords. At a minimum, we require the password to contain a special character, an uppercase letter, a lowercase letter, and it has to be at least 8 characters long.

Register For Free »

How can I manage my account?

Please visit our “getting started” page for information on how to manage your account.

Getting Started »

How do I get my API key?

Our “getting started” page has information about setting up and acquiring your API key. If you need further assistance, our team is ready to help so please visit our support page for information on how to contact us.

Getting Started »

Do you have a free tier to try out the APIs?

Yes, please visit our pricing page to get more information.

Pricing & Plans »

How do you deduct from the quota?

Depending on the API used, the method for quota deduction differs. When using the Fraud API, every API call reduces the quota while for the Enrichment API, the quota gets deducted by how many records are returned by the API call.

Does the quota balance rollover?

At this time, the quota balance does not roll over month-to-month.

When does the quota refresh?

The quota refreshes at the start of your billing cycle. Each cycle is a month, starting from the date of signup.

What languages do you support?

Any programming language that can perform API calls can be used. Please note that we do have example code for popular languages in our technical documentation.

Documentation »

What user or device characteristics can the Fraud API take as input/s and provide ad fraud scores for?

The Ad Fraud API is a service which allows developers to make a request to Pixalate's servers to retrieve the probability (risk score) that a user or device might be compromised or performing a malicious activity. The API can process a user's IP address, device ID, user agent, or any combination of the three.

Ad Fraud API Documentation »

How many apps can I request via the Enrichment API?

One app ID per API request, using the getApp, getCtv, or getDomain methods. Enterprise users gain access to a batch import method which accepts a file containing up to 10k app IDs for each request. Learn more about our Enterprise solution by going to our pricing page.

Pricing & Plans »

Can I get more details about why a particular app is marked for high IVT or not?

Publisher fraud analysis is a service included in our Enterprise solution. Learn more about our enterprise package by going to our pricing page.

Pricing & Plans »

Where can I see a list of data points available to me using the Pixalate Ad Trust & Safety API Suite?

Please visit our KnowledgeBase for more information about this

Knowledge Base »

How do I check my quota balance?

Please visit your account page to check your remaining balance for each API you are subscribed to.

What happens if my quota balance goes to zero? Do you charge for overages?

Overages are charged on the paid tiers.

What currencies can I use?

At the moment we charge in US Dollars.

Where can I get a receipt for my payments?

Receipts are sent to the email address on record each billing cycle after the credit card has been charged.

What pricing tiers do you have?

Please visit the pricing page to view the pricing options for both the Ad Fraud API and the Enrichment API.

Pricing & Plans »

Who can I reach out to if I have any billing issues or questions about pricing?

Please visit the support page to contact us regarding any billing issues or pricing questions.

How can I update my billing information, for example, to provide a new credit card?

Please visit the billing section on your account page to update your billing information.

Account Page »

What is the Supply Chain Object (SCO)?

SCO (Supply Chain Object) is part of OpenRTB and is one of IAB Tech Lab’s privacy standards, meant to work alongside two other standards - ads.txt and sellers.json - to bring transparency to the supply chains involved in a bid request.

Supply Chain Object »

What is SCO Validation & Verification?

SCO Validation ensures that the structure of the Supply Chain Object (SCO) aligns with OpenRTB specifications . It provides a detailed breakdown of structural issues, allowing for quick fixes and minimizing rejection by buy-side platforms.

SCO Verification confirms the accuracy and legitimacy of data within the SCO. By cross-referencing each node with entries in ads.txt and sellers.json, it ensures that all sellers involved are authorized by the publisher, thus reducing the risk of misrepresentation and invalid traffic (IVT).

Q> What are the Validation Reason codes on the SCO V&V API, and what actions are recommended on each?

  • 4101 Missing Version: The SCO submitted does not specify a version, which is essential for determining the correct validation rules.
    • Action: Ensure the SCO includes the ver field with the correct version information.
  • 4102 Missing Complete Flag: The SCO submitted does not contain a complete flag, which is essential for determining if the SCO chain is complete or not.
    • Action: Ensure the SCO includes the complete flag whether the chain is complete or not.
  • 4104 Missing Node ID: A node within the SCO lacks an ID.
    • Action: Ensure every node in the SCO includes a unique ID.
  • 4105 Invalid Node ID Format: The format of the node ID is incorrect.
    • Action: Verify the node ID matches the expected format as per the OpenRTB specification.
  • 4106 Incomplete Node Information: Essential information for a node is missing or incomplete.
    • Action: Check and fill in all required fields for each node.

Q> What are the Verification Reason codes on the SCO V&V API, and what actions are recommended on each?

  • 4401 SCO not provided: The SCO was not provided for these impressions.
    • Action: Ensure the direct partners (and their upstream partners) are passing the SCO.
  • 4402 SCO declared incomplete: The “complete” flag on the SCO was set to 0, indicating it is declared incomplete.
    • Action: Work with partners to address the gaps in the SCO.
  • 4403 Publisher missing in SCO: The first node on the SCO did not point to a publisher.
    • Action: Ensure that the 1st entity in the SCO has a partnership with the associated publisher.
  • 4404 Direct seller not authorized: The 1st seller in the SCO was not listed in the publisher’s ads.txt/app-ads.txt as a DIRECT seller.
    • Action: Ensure that the 1st entity in the SCO is authorized as a seller in the relevant ads.txt/app-ads.txt file.
  • 4405 Reseller not authorized: A seller on a “reseller node” in the SCO was not listed in the publisher’s ads.txt/app-ads.txt
    • Action: Ensure that the 1st entity in the SCO is authorized as a reseller in the relevant ads.txt/app-ads.txt file.
  • 4406 Reseller listed as direct seller: A seller on a “reseller node” in the SCO was not listed in the publisher’s ads.txt as RESELLER, but was listed as DIRECT.
    • Action: Ensure that the 1st entity in the SCO is authorized as a reseller in the relevant ads.txt/app-ads.txt file.
  • 4407 Link in SCO missing in sellers.json: A seller entry in a node on the SCO did not match the sellers.json of the seller on the next node.
    • Action: Ensure that the entity on that node is listed correctly, with the correct seat id in the relevant sellers.json file.
  • 4408 Unable to resolve publisher domain: Unable to resolve publisher domain to get the ads.txt or app-ads.txt
    • Action: Ensure that the correct website or app information is passed. And/or fix the confidential or missing entry in the sellers.json file.
  • 4201 Ads.txt not resolved: The ads.txt for the site was not found.
    • Action: Manually check the location, and work with the publisher to fix the problem.
  • 4202 App-ads.txt not resolved: The app-ads.txt for the app was not found.
    • Action: Manually check the location, and work with the publisher to fix the problem.
  • 4203 Sellers.json not resolved: The sellers.json files for one or more sellers in the SCO were not found.
    • Action: Manually check the location, and work with the seller to fix the problem.

What Our Customers Are Saying

image
François Zolezzi
Head of Supply Quality, Criteo

“MRT offers Criteo access to critical insights helping us evaluate brand safety signals and maintain our quality standards across our in-app supply globally.”


logo-img
image
Eric Bozinny
Senior Director, Marketplace Quality Pubmatic

“Connnected TV and mobile app advertising are both growing, but for buyers to fully embrace the potential opportunity, we need to enhance access to high-quality, brand-safety inventory.”


logo-img