All requests must include valid token and secret parameters for a given platform website. Credentials are available in the Ignite platform Website Info section.

The exceptions to this rule are Agency-scoped endpoints, which require agency_token and agency_secret parameters.

Welcome to the Ignite Platform

The Ignite platform API allows you to retrieve information about audiences, locations, visitors, and products for a given platform website and look-back date.

API Base URL

Unless otherwise noted: GET https://e.atrc.link/api

Entities

  • Websites

    A website with the platform tracking library installed and an active subscription.

  • Locations

    A verified residential location that visits a website and can be resolved to an address.

  • Visitors

    An identified visitor to a website based on their association with a location.

  • Products

    Inventory data about products & items available for sale on websites.

  • Audiences

    A group of visitors with an interest in a product or service on a website.

  • AudienceGroups

    A group of audiences for a website.

  • Opt Outs

    Bulk add email addresses that have opted out of communications.

  • Sales

    Sales data summary for website.

  • Leads

    User-provided website lead data for customer identity match.

Customer POST API

Import customer data into the Ignite platform to match against website visitors.

Look-back Date

Where appropriate, the API will allow you to restrict responses to a given look-back window.

Unless otherwise noted, the look-back date is the start of the date window where an entity was last seen on the website. The default look-back window is 30 days. Or, put another way, by default the API will return entities seen on the website within the last 30 days.

You may over-ride the default look-back window by passing the date parameter in the format YYYY-MM-DD

Example: date=2020-01-20

The max look-back window is 60 days. Requests over 60 days will be defaulted to 30 days.

Hashing Algorithms

Some requests will return hashed email identifiers for entities.

By default, these are MD5 hashes. The API will also return other formats by including the algo parameter in your request.

Example: algo=sha1

Current supported algorithms are: md5 sha1 sha2 . If you require additional formats, please let your account representative know.