On this page:
Dynamic Matched audience overview
Matched audiences use your first-party data (e.g., CRM, NPI lists, voter data) to target specialty campaigns. While generating, IQM’s privacy-compliant Identity Graph links offline and online identifiers across channels and devices, enabling digital targeting of these offline users.
Dynamic Matched audiences are recommended for highly specific PII segments needing continuous refreshes. A key benefit of dynamic Matched audiences is the continuous synchronization between your external data and the IQM platform. Updating your source file automatically refreshes the audience and the identity-matching process, minimizing manual effort.
Refer to Dynamic Matched audience overview for more information, or continue reading to learn more about collaborating with IQM to onboard and target your own dynamic Matched audiences.
Onboard data for a dynamic Matched audience
Data privacy notice: Your organization remains the controller of any personally identifiable information (PII) you send. Ensure all files comply with applicable laws and your privacy policy, and refer to Data privacy measures for dynamic Matched audiences for more guidelines that help ensure security and compliance when sharing data for dynamic Matched audiences. |
The data onboarding process begins outside of the IQM platform, and involves delivering segment files to IQM using an S3 bucket shared between your organization and IQM.
Complete the following steps to onboard your data for dynamic Matched audiences:
Prepare test files
Prepare a test file including 100-1K sample rows for each segment file format you plan to use.
Refer to File formats and schemas to ensure your segment files follow our required column-naming conventions, with any one eligible column mapping selected.
Contact IQM
Contact us at support@IQM.com, or reach out to your account representative, to notify us that you’d like to bring your own data for dynamic Matched audience creation. Include the following details in your message:
Storage location: Specify an S3 region and bucket name. Choose a single region close to data sources.
Confirm the access modal: Choose between a cross-account IAM role or bucket policy. Refer to “Identity and Access Management” (IAM) templates for more details and additional support.
Register seats: Provide one or more seat IDs that are associated with your IQM accounts. Since the seat ID is included in the uploaded path, note that the uploaded audience will be visible only under the specific seat ID used in the path.
Prepare test files: Confirm that you’ve prepared one eligible PII-based file. Do not share the file in your message; IQM will let you know when you can upload the file to the secure, shared S3 bucket.
Your message will signal IQM to create and secure a shared S3 bucket, and provide you with access details for data onboarding via file upload.
Onboard data via file upload
More on data onboarding via file upload: This section includes common AWS CLI examples for data onboarding. However, you can use any S3-compatible tool to complete this process.
CSV files are currently supported. |
Segments:
s3://{bucket}/onboarding/seat_id={seat_id}/{audience_id or folder_name}/{audience_name}.csv
Test and validate
More on setup and processing timelines: Initial setup may take up to one week, which includes automation and testing after access to the shared S3 bucket is granted. This timeline, and the post-setup timelines described below, assume that files land before the top of the hour and pass all validation checks.
Large spikes in volume or schema changes may require more time to process. |
You’ll complete a brief testing-and-validation process before fully onboarding your desired files. This allows you and IQM to address any issues prior to delivering each segment file.
Follow these steps to complete the testing-and-validation process:
Share sample data: In the shared S3 bucket, upload the sample file you prepared: a 100-1K row, PII-based, eligible file for each segment file format you plan to use.
Share validation details (IQM): IQM reviews the details you shared to confirm header, delimiter, and type checks. Refer to Key terms and concepts: Validation check for more information on the items that are validated during this process.
Check the platform for the segments: Verify that the Matched audience(s) appear in the Audiences app for the correct account seat. It may take up to three hours for the segments to become available in the IQM platform.
After the testing and validation process is complete, use the same paths to upload your complete files for dynamic Matched audience creation.
Manage a dynamic Matched audience
You can use the Audiences app to review and manage Matched audiences. You’ll follow the same process as you would if you created a standard Matched audience.
Refer to Create or manage a Matched audience for step-by-step instructions.
Target a dynamic Matched audience
Standard and dynamic Matched audiences are targeted in the same way: via new or existing campaigns from the Audiences app or Campaigns app.
Refer to Create or manage a Matched audience for step-by-step audience targeting instructions.
Refresh a dynamic Matched audience
More on audience refreshes: Note that uploading a file with the same name under the same path as a previous upload will automatically refresh the existing audience data—not create a new audience.
The newly uploaded file must follow the same column mapping as the original upload. If you intend to change the column mapping (e.g., add or remove columns), notify IQM prior to upload. |
You can dynamically refresh an existing, successfully created audience to change the number of records it includes; or dynamically refresh a failed audience to correct any issues.
Adjust an audience’s record count
Follow these steps to refresh an existing audience by changing its record count:
Select a previously successful audience.
Modify the file’s content.
Confirm that the mapping, name, and column names are consistent with the existing audience.
Uploading a file with the same name and path as the existing audience, but with changes applied to the column mapping, will cause the audience creation to fail. Always notify IQM prior to upload if you intend to change the column mapping (e.g., add or remove columns).
Save your changes to the existing file.
The audience will reprocess to reflect the newly added data. Note that it may take up to three hours for the Matched audience to become available in the IQM platform. The time it takes for the audience to be ready varies and may take up to three hours for PII-based audience creation or refresh.
Fix a failed audience
Follow these steps to refresh a previously failed audience by correcting any issues:
Select an audience that previously failed due to an invalid column header, combination, or file content.
Correct the file.
Refer to Validation check and File formats and schemas for additional support.
Reupload the corrected file to the same path with the same name.
The audience will reprocess to reflect the newly added data. Note that it may take up to three hours for the Matched audience to become available in the IQM platform. The time it takes for the audience to be ready varies and may take up to 24 hours for PII-based deliveries.
Locate additional Matched audience resources