Prepare your data for import

Keep your data fresh

You must ensure your data is refreshed in the data source before a manual or scheduled connection run in order for that data to be imported for use in the intended destination or use case. For example, if you choose a daily schedule, you need to refresh your data on a daily basis, before the scheduled start time.

---

Make your data available

All use cases require one table or dataview per conversion event or audience list. To use the same data source for an additional conversion event or audience list, you need to create an additional table or dataview.

Some data sources require you to have proper credentials in order to make the connection, while others require that the data be accessible by Data Manager's services. Check the specific guide for the data source you're using for specific guidance.

---

Format your data

The following sections show you how to properly format your data. Keep them in mind to ensure it can be imported without error.

About file formats

If you are uploading a file, such as a CSV file, the first line of the file must contain the headers.

Ensure that the file has an extension, as files without extensions are rejected.

About date and time formats

Data Manager supports converting dates and times of various formats into a logical timestamp, based on six templates using three format sets: DATE, TIME, and TIMEZONE. Data Manager does not support the DATETIME type. DATETIME fields need to be converted to the STRING type in the data source, using the supported formats described in this article.

The following are examples of timestamps in supported formats:

• 2012-08-15T00:01:54Z (UTC ISO 8601 Standard)
• 2012-08-14T17:01:54-07:00 (ISO 8601 Standard with Offset)
• Aug 14, 2012 17:01:54
• 08/14/2012T5:01:54 PM
• 2012-08-14 5:01:54 PM
• 08/14/2012 17:01:54
• 2012-08-14 17:01:54
• 08/14/2012 17:01:54*123
• 2012-08-14T17:01:54-07
• 08/14/2012T17:01:54-0700
• 2012-08-14T17:01:54-070000
• 2012-08-14T17:01:54-07:00:00
• 2012-08-14T17:01:54 America/Los_Angeles
• Aug 14, 2012 17:01:54PST
• 2012-08-14 17:01:54 PST
• 2012-08-14 17:01:54 Pacific Standard Time
• 2012-08-14 17:01:54 GMT-07:00
• 08/14/2012 17:01:54 GMT-07:00:00

About hashing private customer data

To keep your data secure, private customer data that you import should be hashed. Data Manager will hash the data for you using the SHA256 algorithm, which is the industry standard for one-way hashing. The result is hex encoded. You don’t need to pre-format your data. Data Manager will normalize relevant PII (personally identifiable information) fields, perform hashing and encoding for you, and push the data to the API for your use cases.

If you prefer to hash private customer data yourself, check Format your customer data file to ensure it’s formatted correctly. If you upload a hashed data file, don’t hash non-private customer data. Data Manager will push your hashed data to the API.

Note that smart hashing is automatic, meaning you will not need to select anything from the Actions menu.

---

Define the scope of your data import using filters

Data Manager lets you set filter conditions directly in the UI, eliminating the need to create custom data pipelines or write complicated SQL queries within your data source. When you create a filter, Data Manager only imports data from your data source (for all use cases) that satisfies all of the filter conditions.

You can apply one filter with up to 25 conditions per connection.

Create a filter

To create filters for a new data connection, add them during the Select data stage of setup:

1. From the Select data step of setup, click Filterto expand it.
2. Select the field to use to filter your data.
3. Select an operator.
4. Enter a value.
5. Optional: Create additional conditions, by clicking Andor Or.
6. Continue the setup process.

To create and edit filters for an existing data connection:

1. From the Data manager screen, click on the connection name to edit it.
2. Under Filter, click Edit.
3. Make your changes.
4. Click Save.

Supported operators

• AND
• OR
• Doesn’t contain (strings, integer, date, time, Boolean)
• Contains (strings, integer, date, time, Boolean)
• Greater than (integer)
• Equal to (integer, string, date)
• Less than (integer)
• Before (date, time)
• After (date, time)
• Does not equal
• Starts with
• Ends with
• Does not start with
• Does not end with

Supported data types

• Currency
• Date
• Time
• Boolean
• Integer
• Dropdown (for example, a Salesforce picklist type)
• String

---

Search Ads 360 specific Identifiers

To successfully upload offline first-party data to Search Ads 360 using the Search Ads 360 / Data Manager integration, your conversion data needs to include specific identifiers. For Search Ads 360 to correctly attribute these conversions, you must provide at least one of the following: dclid, gclid, matchId, mobileDeviceId, or impression_id.