Site Attribution Tag

To properly measure the results of your account based marketing programs with Madison Logic we will provide your team with a ‘tag’ (also referred to as a pixel) which should be implemented on your company’s website. This pixel is similar in function to those that you may have already implemented such as Google Analytics, Mixpanel, Marketo, or Eloqua. The Madison Logic pixel will enable proper measurement of website visits from your target accounts, as well as linking your Madison Logic advertising programs with your website activity.

Madison Logic does not collect any personally identifiable information with this tag. We simply record which companies are visiting your website and present this information back to you. Website visit activity collected from your site is never shared with any other clients of Madison Logic, it is never shared with external partners, nor is it used for behavioral targeting purposes across other clients or products.

When a visitor from a targeted account visits your website, the Madison Logic pixel will read the visitors cookie or mobile device ID. This cookie or mobile device ID is then referenced against our data management platform that maintains a list of companies and their respective cookies and mobile device IDs.

How is the tag deployed?

The Madison Logic tag should be deployed on every page of your website. Place the tag just below the opening head tag <head> of each page.

Async or Defer attributes can be placed after the tag based on your company's preferences.

What data are you collecting from the site tag?

The following data points are collected by Madison Logic

Visitor cookie or mobile device ID
Date/time of visit
Fixed variable (client's domain) which is a hard-coded into the tag

Where do you store the site data?

Madison Logic stores your data in the United States, in the state of Virginia, within the Amazon Web Services region us-east-1

How is my data secured in transit?

When Madison Logic retrieves your data it is secured in transit by encryption using TLS 1.2.

How is my data secured at rest?

Your data is secured at rest by encrypting it using AWS Key Management Service APIs.

AWS KMS uses the Advanced Encryption Standard (AES) algorithm in Galois/Counter Mode (GCM), known as AES-GCM. AWS KMS uses this algorithm with 256-bit secret keys.

How Is my data protected from other customers?

Access to your data is programmatically restricted by customer via a third party authentication & entitlements service (Okta).

Is there a process in place for removing our content and data at the end of the use agreement?

Yes. We can ensure that your content is securely removed from Madison Logic systems. Contact us for more information.

What type of compliance and controls are in place?

Security and quality controls in Amazon Web Services have been validated and certified by the following compliance schemes:

AWS Service Organization Controls (SOC 1, SOC 2, and SOC 3) Reports. You can request a copy of these reports from AWS Compliance.
PCI DSS Level 1. For more details on PCI DSS compliant services in AWS, you can read the PCI DSS FAQs.
ISO 27017. For more details on ISO 27017 compliant services in AWS, you can read the ISO-27017 FAQs.
ISO 27018. For more details on ISO 27018 compliant services in AWS, you can read the ISO-27018 FAQs.
ISO 9001. For more details on ISO 9001 compliant services in AWS, you can read the ISO-9001 FAQs.
In evaluation for FIPS 140-2. For more details, you can view the FIPS 140-2 Implementation Under Test List.

Who owns the site data?

The client owns all data derived from implementation of the site tag and grants Madison Logic the right to use the data for reporting purposes only. The data can not be sold by Madison Logic to any 3rd party sources. Details for all data usage are called out in your MSA.

How can users opt-out of the site pixel?

Users can opt out of all Madison Logic tracking via http://go.madisonlogic.com/RequestMyInfo.html

Language from Madison Logic's privacy page can be viewed her https://www.madisonlogic.com/privacy/