Request a Production Key

Applying for a Production Key

Ready to apply for a production key? If so, click the button to start the process of activating your Acxiom application. Otherwise, read below for instructions on how to apply.

Apply for a Production Key

You've built and tested your application on the Data Services API Platform using test data, and you are ready to take your application into production. Congratulations! The rest of this page is dedicated to helping you through the process of acquiring a production key and going live with the Data Services API Platform.

The registration process for a production key on the Data Services API Platform is a bit more extensive than for most other API platforms you may work with. This is because much of what people use with Acxiom, or buy through either Acxiom or Acxiom-based applications, is first- or third-party data. Therefore, both Acxiom and its partners have to be extremely thoughtful about the applications that run on the platform, how they plan to use data, and how they or an end user might inadvertently use data in a way that violates privacy or other regulations.

Certain types of applications will definitely not be approved for a production key on the Acxiom API platform. In general, applications that are excluded are those that:

  • Expose personally identifiable (PII) data to third parties without the end user’s explicit permission.
  • Behaviorally target children and teens under 18 years of age to use the service.
  • Allow the presentation of Acxiom data in a bulk format in response to a query.
  • Use any robot, spider, site search/retrieval application, or other device to retrieve or index any portion of the Acxiom’s data, or permit any third party to do the same.
  • Allow or facilitate the use of Acxiom data for credit granting, credit monitoring, account review, insurance underwriting, employment, background screening or any other purpose covered by the Fair Credit Reporting Act.
  • Allows or facilitates the use of Acxiom’s data as a derivative database to verify, confirm, enhance, audit, update, or develop any files, products, or databases owned, licensed, or marketed by other companies.

These are only some examples. Each application is reviewed in detail by our legal and privacy teams to ensure compliance with all applicable laws and regulations, as well as industry best practices.


  • Primary Contact.This is the person who will be the interface for all communications between your team and the Acxiom activation team. This is the person who the activation lead will call or email first, as well as the person who will be cc’d on all team communications. The field is prepopulated with the user information for your login.
  • Organization Name.The name of the organization associated with your login. You may change this entry if the organization which will be publishing the application is different from what is shown.
  • Technical Contact.This is the primary developer or engineering team lead who we should engage for detailed questions concerning how the application functions.
  • Acxiom Account Representative.Please fill in the name of your Acxiom account team leader if you already have a relationship with Acxiom. The activation team will immediately reach out to that individual and integrate them into the approval process. Your account representative can be a valuable resource for working with internal Acxiom teams to shepherd the process on your behalf.

When you have completed the form, click ‘Send Request'. This submits your request to our customer activation team who will follow up to start the approval process. You will be assigned an activation lead who will be your main contact through the entire approval process. Your support request information will display once the form has submitted successfully. At this point, you may add any other comments that you believe are important for us to know.

FIRST CONVERSATION WITH YOUR ACTIVATION LEAD

You will receive a call from your activation lead during their hours of support, which are Monday through Friday 8:00 am - 5:00 pm CST. The activation lead will review your application with you. They will also review the rest of the steps in the process. At the same time, they may ask for a test log-in (for SaaS services) or a time to receive a demo of your application.

If you indicated that you have an existing Acxiom account representative, the activation lead will notify them of your application. Your account representative will become your champion in the activation process. How they participate is flexible and depends on their relationship with your organization. They may attend many if not all of the activation meetings set up with your activation lead. They will be copied on all email communications. Most importantly, they will be involved in negotiating your contract for use of the API services.

ACTIVATION PROCESS

Several things occur during the activation process.

  1. Your Acxiom account representative (or in the case of a new customer, a new representative) will contact you to discuss your application and the data/services that it requires to launch. At that time, you and the representative will review contract terms and conditions. In all cases, a signed contract between Acxiom and the developer laying out the terms and conditions of the relationship will be required before activation occurs.
  2. The activation team reviews your (software) application to understand what it does, its intended use, how it acquires and manages first- and third-party data, whether its approach to security is comprehensive, how third-parties (e.g. Acxiom customers) will be authenticated and authorized to use it, and other aspects needed to ensure that the application complies with the Acxiom terms of service (which you signed when you registered on the Developer Connection), your contract, and all applicable regulations and laws.
  3. As part of step 2, depending on the type of data your application uses and that you are storing, you may be asked to submit an example of the data fields used by your application that contain first- or third-party data, whether individual or aggregate (segment). This can be in the form of a .xls or .csv file with the fields names as row headings and a sample of data. Alternately, if you are maintaining a large number of features (fields) about individual, you can submit a .doc or .pdf containing feature name and a description. Your activation lead will work with you to determine if Acxiom will need this information in order to approve a production key.
  4. We may recommend changes to your application, based on our knowledge of the APIs, which can improve the capability or performance of your application with minimal effort prior to activation. These are recommendations, and you would not be required to implement them prior to receiving a production key.
  5. If changes to your application are required to ensure compliance with all laws, contracts, and terms of service, our activation team will work with you to find the best solution to the specific issues to ensure that you can quickly adapt your software and move into production.
ISSUING A PRODUCT KEY

Once your application is approved through the activation process and your contract is signed, the activation team will enable your application on the Acxiom API Platform, which includes:

  • Your Acxiom account representative (or in the case of a new customer, a new representative) will contact you to discuss your application and the data/services that it requires to launch. At that time, you and the representative will review contract terms and conditions. In all cases, a signed contract between Acxiom and the developer laying out the terms and conditions of the relationship will be required before activation occurs.
  • The activation team reviews your (software) application to understand what it does, its intended use, how it acquires and manages first- and third-party data, whether its approach to security is comprehensive, how third-parties (e.g. Acxiom customers) will be authenticated and authorized to use it, and other aspects needed to ensure that the application complies with the Acxiom terms of service (which you signed when you registered on the Developer Connection), your contract, and all applicable regulations and laws.
  • As part of step 2, depending on the type of data your application uses and that you are storing, you may be asked to submit an example of the data fields used by your application that contain first- or third-party data, whether individual or aggregate (segment). This can be in the form of a .xls or .csv file with the fields names as row headings and a sample of data. Alternately, if you are maintaining a large number of features (fields) about individual, you can submit a .doc or .pdf containing feature name and a description. Your activation lead will work with you to determine if Acxiom will need this information in order to approve a production key.
  • We may recommend changes to your application, based on our knowledge of the APIs, which can improve the capability or performance of your application with minimal effort prior to activation. These are recommendations, and you would not be required to implement them prior to receiving a production key.
  • If changes to your application are required to ensure compliance with all laws, contracts, and terms of service, our activation team will work with you to find the best solution to the specific issues to ensure that you can quickly adapt your software and move into production.
QUESTIONS

Have more questions? Please contact our customer service team who will be happy to answer any questions you may still have.