Skip to main content

The Google Store Sales Direct Attribution Program

With LiveRamp’s Google Store Sales Direct (GSSD) integration with Google Ads, LiveRamp can import your offline conversion data directly into Google Ads (rather than you having to put a third-party tracking tag on your site). Google matches the customer information tied to your conversion data with Google user information to create conversion reports in Google Ads. These reports provide advertisers with aggregated and anonymized conversion data that allows them to understand the value of their Google Ads campaigns. Ad exposure data does not leave the Google platform.

Note

For information on LiveRamp's privacy policies, see our Privacy page.

GSSD is a Google-paid program, so there is no additional cost for brands and advertisers to use this program.

Note

Google must approve program participants. Contact your LiveRamp or Google rep to find out about getting approved for GSSD.

Tip

Some customers might also qualify for LiveRamp’s Google Store Sales Improvements (GSSI) attribution program, which unlocks additional capabilities such as store visit and sales measurement, smart bidding capabilities, and enhanced reporting and measurement.

Eligibility is based on vertical (currently only Retail and QSR) and general requirements (technical thresholds). Contact your LiveRamp or Google rep to to confirm your eligibility and find out about getting approved for GSSI.

How Google Sales Store Direct Works

  1. A Google user is logged in (such as by logging in to Chrome or to Gmail) on Search, Gmail, or Shopping and then clicks on an ad.

  2. The user then visits your store and purchases an item. You are able to link the transaction to a customer (e.g., by loyalty program or e-receipts).

  3. You send conversion data tied to PII to LiveRamp.

  4. LiveRamp normalizes and hashes your PII and uploads the conversion data to Google.

  5. Google then matches the hashed PII to the Google IDs of logged-in users in order to match your offline conversion data to ad clicks and then extrapolates to report for all clicks.

Store sales conversion data will be available in Google Ads within 1-2 days of data upload.

Overview of Steps Involved

The following steps need to be performed to enable the attribution analysis in Google:

  1. You complete any necessary legal agreements with LiveRamp.

  2. You fill out a form LiveRamp sends you to provide us with the required setup information.

  3. You grant LiveRamp access to your Google Ads account by performing OAuth authorization.

  4. You agree to the Custom data policies in the Google UI by performing the steps in step 3 of Google’s instructions, and then a conversion action is automatically created in your Google Ads account.

  5. You upload a test file to LiveRamp so LiveRamp can confirm that Google will accept the file.

  6. You upload 90 days of continuous conversion data to LiveRamp, as required by Google’s algorithms for the Store Sales program.

  7. You activate the campaign.

  8. LiveRamp processes the data and delivers your data to your Google Ads account.

  9. You set up an automated data upload process so that new transaction data are uploaded every day.

  10. LiveRamp normalizes and hashes your PII, and delivers your data to your Google Ads account.

  11. You view the attribution analysis in Google Ads.

See the appropriate sections below for more information on performing these steps.

Provide LiveRamp with Setup Information

The LiveRamp technical team will send you a Google form to fill out that includes the required setup information:

  • Email address of Google Ads Admin User

    Tip

    To determine who the Google Ads Admin User is:

    1. Navigate to the specific MCC (My Client Center) account being used for upload

    2. Go to Tools > Setup > Account Access (the wrench icon in the upper right)

    3. Confirm the email address for an Admin user

    Note

    In the future, if the admin changes, please notify the LiveRamp team as to who the new admin will be, as the new admin will need to complete the OAuth step again.

  • Loyalty Rate: The percentage of overall sales that are identifiable (i.e., associated with any customer information such as email, home address, phone number, etc), represented by a number between 0 and 1. For example, if 25% of your sales are identifiable, your Loyalty Rate would be .25.

  • Transaction Upload Rate: The percentage of transactions uploaded (out of transactions identified with any customer information), represented by a number between 0 and 1. For example, if you upload 50% of the sales that you are able to associate with a customer, your Transaction Upload Rate would be .5.

  • MCC ID associated with your account on Google Ads.

Caution

Make sure that you are authenticating with the correct MCC-level Google Ads account number, and that you have “write” access to the account. LiveRamp will collect the MCC account number that the OAuth grantor is added to via the set-up form.

Grant LiveRamp Access to Your Google Ads Account

Once we’ve performed actions on our end to create the required destination account tile, the Google Ads admin user needs to perform OAuth authorization in Connect to grant LiveRamp permission to upload offline conversion data into your Google Ads account.

Note

The Google Ads admin user must be an admin on the MCC account LiveRamp is uploading data to.

  1. Log into Connect with the credentials received via email from LiveRamp.

  2. If your company is operating multiple accounts with LiveRamp, make sure that the correct account is selected (this is usually some variation on your company’s name). You can change accounts by clicking anywhere in the account switcher area and then using the account drop-down list to select the desired account.

    C-Global_Nav_Announcement-account_switcher.png
  3. From the Connect navigation menu, click Destination Accounts to navigate to the Destination Accounts page.

    C_Onboarding-My_Destinations_menu-selection.jpg
  4. Locate the appropriate Google Store Sales destination account tile (see figure below).

    Note

    You may have more than one tile if your company has additional data transactions with LiveRamp. For Google Store Sales, the tile name will be “[Your Company]” GA AW 2.0.

    GSSD DA Tile.jpg
  5. Click the ellipsis (three dots) that appears when you hover over the lower right corner of the tile, and then select Settings.

  6. In the Edit Account page, click Authorize.

  7. From the OAuth popup window that opens, enter the email associated with the Google Ads account.

  8. Click Allow.

  9. In the Edit Account page, click Save.

  10. Email googlestoresalesdirect@liveramp.com to confirm that you have completed the authentication process.

Format the File

Before sending your conversion data to LiveRamp, make sure to strictly follow the guidelines listed below:

Note

If any guidelines listed here conflict with the guidelines in our general file formatting instructions, follow these guidelines.

Caution

If an uploaded file does not meet these requirements, you will need to reformat the file until it is formatted correctly.

  • Headers must be included in the exact order as listed below.

  • If hashing email addresses, convert all characters to lowercase and remove all whitespace before hashing. For example, the plaintext email address "MyName@liveramp.com " must be changed to "myname@liveramp.com" before hashing.

  • This attribution program uses our File-Based Recognition workflow. Make sure to follow our recommended file limits for File-Based Recognition workflow files (such as a maximum of 500,000,000 rows per file and a maximum uncompressed file size of 50 GB).

  • Your conversion data file must use one of our allowed delimiters (commas, tabs, or pipes), and be one of our allowed file types (.csv, .tsv, .psv, or .txt).

  • Include all of the required columns listed below.

  • Fields must not have leading or trailing white space.

  • Unless values are required for a field, fields can be left blank if there is no data for the given row (do not include “N/A” or “null”).

  • The file must be rectangular. That is every row must have the same number of delimiters and columns of data.

Tip

To download an Excel file template that contains all possible columns and formatting instructions, click here.

After transferring your data into the file template, be sure to delete the row with the formatting instructions and save the file in one of our allowed file types (.csv, .tsv, .psv, or .txt) before uploading.

Once the file has been formatted correctly, upload the file to LiveRamp. See the “Upload the File” section below for more information.

Field Name

Column Required?

Values Required?

Notes

first_name

Yes

Yes (if name and postal address (NAP) is used as an identifier)

last_name

Yes

Yes (if NAP is used as an identifier)

address_1

Yes

Yes (if NAP is used as an identifier)

address_2

Yes

No

  • Include values in this column if you have additional street address info for a given row.

city

Yes

Yes (if NAP is used as an identifier)

state

Yes

Yes (if NAP is used as an identifier)

  • Must be a two-character, capitalized abbreviation ("CA", not "California" or "Ca").

zip

Yes

Yes (if NAP is used as an identifier)

  • ZIP codes can be in 5-digit format or 9-digit format (ZIP+4).

email_1

Yes

Yes (if email address is used as an identifier)

  • Must be plaintext or SHA-256 hashed.

  • If you have multiple emails for a consumer, send your best one in the “email_1” column.

email_2

Yes

No

  • Must be plaintext or SHA-256 hashed.

email_3

Yes

No

  • Must be plaintext or SHA-256 hashed.

email_4

Yes

No

  • Must be plaintext or SHA-256 hashed.

transaction_category

Yes

Yes

  • The conversion action for the transaction.

  • Can include up to 10 conversion actions per account.

transaction_timestamp

Yes

Yes

  • Corresponds to the date/time of the transaction in UTC - (example: “2017-02-07T13:25:00Z-0800" should be the time the conversion happened in UTC).

  • Standard formats:

    • yyyy-MM-dd

    • yyyy-MM-dd'T'HH:mm:ss'Z'-0000 (for example, 2021-06-04T10:01:00Z-0000)

  • Additional formats:

    • MM/dd/yyyy hh:mm:ss aa

    • MMM dd,yyyy hh:mm:ss aa OR MMM dd,yyyy

    • MM/dd/yyyy HH:mm:ss

    • yyyy-MM-dd HH:mm:ss OR yyyy-MM-dd

    • yyyy-MM-ddTHH:mm:ss OR yyyy-MM-dd

    • yyyy-MM-dd HH:mm:ss+z OR yyyy-MM-dd

    • yyyy-MM-ddTHH:mm:ss+z OR yyyy-MM-dd

transaction_amount

Yes

Yes

  • Do not include any (currency) symbols.

  • Format required: XXX.XX

  • Only include USD amounts. If your transaction data contains international currency amounts, convert your amounts to USD prior to sending your data.

phone_1

Yes

Yes (if phone number is used as an identifier)

  • Do not include any hyphens or parentheses.

  • Must be plaintext.

phone_2

Yes

No

  • Do not include any hyphens or parentheses.

  • Must be plaintext.

order_id

No

Yes (if this column is included in the file)

  • A unique ID that corresponds to the order that the particular item belongs to, which is used to deduplicate data.

  • Do not include special characters, currency symbols, or commas.

quantity

No

No

  • Number of items sold.

  • If the quantity parameter is populated, then the conversion value amount (the "transaction_amount") should represent the total after multiplying for the quantity.

  • If blank, the default value is "1".

  • This optional column can be used when participating in Google's Co-Op program.

product_id

No

Yes (if this column is included in the file)

  • An alphanumeric value delineating a unique item in an order.

  • Do not include special characters, currency symbols, or commas.

  • This column is only leveraged for Google Store Sales Improvements.

  • Common product identifier types include UPC, ISBN, Brand, and MPN (see Google's documentation for more information).

  • This optional column can be used when participating in Google's Co-Op program.

store_code

No

Yes (if this column is included in the file)

  • A "shop code." A unique ID that clients assign to each of their store locations.

  • Must not be longer than 64 characters.

  • No special characters (i,e., "<" or ">") or contain a URL.

  • This column is only leveraged for Google Store Sales Improvements.

country_code

No

No

  • The CLDR territory code of the country associated with the respective merchant center feed where your items are uploaded (e.g., US).

  • This optional column can be used when participating in Google's Co-Op program.

language_code

No

No

  • The ISO 639-1 language code of the language associated with the respective merchant center feed where your items are uploaded (e.g. EN).

  • This optional column can be used when participating in Google's Co-Op program.

merchant_id

No

No

  • The Merchant Center ID that contains the associated merchant center feed and item.

  • This optional column can be used when participating in Google's Co-Op program.

custom_[field_name]

No

Yes (if this column is included in the file)

  • A “Custom Variable” set in Google Ads. The values within this field are referred to as “custom values”.

  • You can have up to a total of 20 custom values per each Custom Variable. At this time, Google is only allowing one Custom Variable.

  • Each row can contain only one custom value.

  • Allows you to group conversions by product groups, customer type, or conversion channels (e.g., in-store sales or phone sales), etc.

  • The custom field column heading must start with "custom_", followed by the field name. For example "custom_brand_name" would translate to a Custom Variable called “brand_name” in Google Ads.

  • This column is only leveraged for Google Store Sales Improvements.

Header Row Example

first_name|last_name|address_1|address_2|city|state|zip|email_1|email_2|email_3|email_4|transaction_category|transaction_timestamp|transaction_amount|phone_1|phone_2|order_id

Conversion Data Examples

Alex|Chen|44 Main Street|#12|San Francisco|CA|94100|alex@gmail.com|ac@ymail.com||||In-store|2014-03-31|99.99|1234567890||52389

Julian|Roodiger|55 Mission Street||San Francisco|CA|94500|julian@gmail.com||||PhoneSales|2014-03-30|55.55|2223334444||98740

Send Conversion Data to LiveRamp

To set up the integration, first send LiveRamp a test file that follows the format outlined below. The test file should contain only about 20 rows of data.

Once we’ve confirmed that Google can accept your test file, send a file that contains the most recent 90 days of continuous conversion data. In other words, provide a backfill file containing at least one transaction every day for the previous 90-days.

Once your campaign has started, send conversion data to LiveRamp at your preferred cadence (daily or weekly). Google and LiveRamp strongly recommend that you upload conversion files on a daily basis to provide the most up to date reporting and minimize any risks of data gaps.

Tip

Most customers automate this process to send files on a regular cadence.

Caution

The Google Store Sales program requires that at least 6,000 unique transaction events be uploaded over a 28-day period.

Conversion Data Guidelines

Each conversion data record must include at least one PII identifier (name and postal address, email, or phone) and the required conversion data:

  • Transaction category

  • Transaction timestamp

  • Transaction amount

If you are able to provide these additional fields, it is highly recommended that you do for better tracking and reporting:

Note

These fields are only leveraged in Google Store Sales Improvements.

  • Order ID (optional but recommended)

    Note

    The "order ID" field is required for most other LiveRamp attribution programs.

  • Product ID (individual items purchased)

  • Store ID

  • Custom field

Do not include any other conversion data (such as quantity).

Make sure to also follow these additional guidelines:

  • Put your best email and phone in the first fields for those.

  • Avoid sending duplicate transactions (transactions already sent to LiveRamp). If you send weekly or monthly files, only send transactions that occurred since the previous file was sent.

  • Do not include conversions with a conversion date in the future.

Follow the instructions in the "Format the File" section for the sample file and all subsequent files.

Upload the File

Upload conversion data files using LiveRamp’s SFTP server or your SFTP server.

You can also have us pull files from an AWS S3 bucket or GCS bucket. See “Getting Your Data Into LiveRamp” for more information.

Caution

Files for Google Store Sales cannot be uploaded via Connect.

  • To upload files using LiveRamp’s SFTP: Use the credentials provided for you by your technical contact once the agreement has been signed and follow the instructions in “Upload a File via LiveRamp's SFTP”.

  • To upload files using your SFTP: Follow the instructions in “Upload a File via Your SFTP”.

Once the file is uploaded, information on file processing status can be viewed in Connect (see "Check File Processing Status" below for more information).

Tip

Upload transactions on a daily basis to provide the most up to date reporting and minimize any risks of data gaps.

Most customers automate this process to send files on a regular cadence. Use the same SFTP subdirectory or S3 bucket that you used to upload your sample conversion data. Google strongly recommends that you upload conversion files on a daily basis to provide the most up to date reporting and minimize any risks of data gaps.

Check File Processing Status

You can check the status of the files you've uploaded on the Files page in Connect. See "Check the Status of an Uploaded File" for complete instructions.

Note

Once you've uploaded a file, it can take up to 20 minutes before the file appears associated with the appropriate audience(s) on the Files page. If the file does not appear after at least 20 minutes, create a support case.

Files for this attribution program use our File-Based Recognition (FBR) workflow, and so the column headings that display on the Files page will look different from the ones that display for files that use our Onboarding workflow.

Because the PII in the files is passed through (and not matched), the recognition rate will be zero.

When you open the details pane on the Files page, all of the stats for RampIDs will always show “0” since we are simply passing through the PII and not matching to RampIDs.

FAQs

Upload transactions on a daily basis to provide the most up-to-date reporting and minimize any risks of data gaps.

This typically takes 2-4 days after LiveRamp has received your data.

Any questions related to conversions or reporting should be directed to your Google representative.

The agreement enables you to:

  • Send transaction files that are not counted towards your Onboarding Agreement.

  • Participate in any of LiveRamp's "platform-paid offline attribution" programs, subject to mutual agreement between LiveRamp and the brand. These additional offline attribution programs include Google Campaign Manager Offline Conversions API, Pinterest, Bing, etc.

Those fees only apply if there are significant changes to file formatting that cause a file to fail or if a file is dropped in the wrong location. However, our team will reach out and offer the opportunity to correct the issue (in which case no fee would be applied). The pricing verbiage is standard language to remind participants to be mindful about file formatting and location drop.

Yes. Clients may have multiple MCC IDs because they have sub-brands with transaction data all coming over in one file feed.

Yes. Brands can use multiple conversion actions (up to 10) to differentiate among transactions in a file feed (i.e. retail store versus outlet). This is common with data among sub-brands as well.

If a brand is broadly approved, whether they want to enroll certain sub-brands as a separate advertiser is up to them. Contact your Google rep for more information.

Data files are exclusively used for store sales measurement and in combination with ad products used by you (such as Google Store Visits and Customer Match audiences).

You may take the file you are working with for the Google Campaign Manager Offline Conversions API program and perform the following actions in order to use it with Google Store Sales Direct (see “Enable Offline Conversion Data in Google DV360 with the Campaign Manager Offline Conversions API” for more information):

  1. Add a “transaction_category” field in the order shown below. If desired, you can use one of your Floodlight custom variable (U variable) fields and rename the column to “transaction_category”.

  2. Change the column heading for "ordinal" to "order_id."

  3. Remove the following fields:

    • Conversion_Quantity

    • Floodlight custom variable IDs (“U1”, “U2”, etc.)

The modified file should have these fields in the order shown below:

  • first_name

  • last_name

  • address_1

  • address_ 2

  • city

  • state

  • zip

  • email_1

  • email_2

  • email_3

  • email_4

  • phone_1

  • phone_2

  • transaction_category

  • transaction_timestamp

  • transaction_amount

  • order_id

If you are interested in enabling the YouTube measurement feature enhancement, contact your Google rep to confirm eligibility and determine your allow-listing status. In regards to the setup, if YouTube sits under the same MCC used for Store Sales Direct or Store Sales Improvements, then it can be enabled easily. If it sits under a separate MCC ID, then the MCC will have to be set up for Store Sales and the implementation steps will need to be completed again.