Skip to main content

The Nextdoor Conversions API Program for Offline Conversions

The Nextdoor Conversions API Program for Offline Conversions enables advertisers to send offline conversion data to Nextdoor. Nextdoor performs attribution analysis on the impact of that advertiser’s Nextdoor campaign on offline conversions. This allows customers to understand how Nextdoor campaigns drive offline conversions and to find additional data to better optimize ad spend or customer experience.

Note

The Nextdoor Conversions API Program for Offline Conversions was formerly known as "the Nextdoor Attribution Program"

Nextdoor must approve all program participants. Contact your LiveRamp or Nextdoor rep to find out about getting approved for the Nextdoor Attribution program.

Overview of Steps Involved

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

  1. Before your campaign starts, you send LiveRamp a sample conversion data file so we can test the integration with Nextdoor.

  2. You activate your campaign.

  3. You send offline conversion data with PII to LiveRamp.

  4. LiveRamp matches the PII to Nextdoor IDs and then delivers matched data to Nextdoor.

  5. You request an attribution report from Nextdoor with your desired settings.

  6. Nextdoor sends you an offline conversion report for your Nextdoor campaign.

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

Format the Conversion Data File

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.

Note

Once you set up the file format for an existing conversions program feed, try to keep the file format (such as the column headers or the column order) the same for all subsequent files. If you change the file format for an existing feed, create a support case before uploading the new file to ensure your existing feeds are not impacted. For more information, see "Changing the Format of an Existing File".

List of All File Columns

See the table below for a list of columns and formatting instructions:

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)

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

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

email_2

Yes

No

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

email_3

Yes

No

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

email_4

Yes

No

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

transaction_category

Yes

Yes

  • A category or segment that the transaction is in (for example, “category_1”).

  • All rows in files for the same campaign should contain the same transaction category value.

transaction_timestamp

Yes

Yes

  • Corresponds to the date/time of 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 h:mm:ss aa

    • MM,dd,yyyy h:mm:ss

    • MM/dd/yyyy HH:mm:ss

    • yyyy-MM-dd HH:mm:ss

    • yyyy-MM-dd'T'HH:mm:ss

    • yyyy-MM-dd HH:mm:ssZ

    • yyyy-MM-dd

transaction_amount

Yes

Yes

  • The transaction amount.

  • Do not include any (currency) symbols.

  • Format required: XXX.XX

phone_1

Yes

Yes (if phone number is used as an identifier)

  • Do not include any hyphens or parentheses.

  • Can be plaintext or SHA-1 hashed.

  • If you have multiple phone numbers for a consumer, send your best one in the “phone_1” column.

phone_2

Yes

No

  • Do not include any hyphens or parentheses.

  • Can be plaintext or SHA-1 hashed.

order_id

Yes

Yes

  • A unique ID (such as a transaction ID) that corresponds to the order that the particular item belongs to (this is often referred to as an “ordinal”). If the value is not unique, a partner may deduplicate some of these events when ingesting your conversion data.

  • To measure item-level events, the value will need to be a unique value for each item within a basket. LiveRamp recommends using the concatenated value of the order ID + product SKU. For example, if the order ID is “123” and SKU is “456”, the “order_id” value would be “123456”.

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

custom_field_1

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_2

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_3

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_4

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_5

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_6

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_7

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_8

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_9

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

custom_field_10

Yes

No

  • A text field to share values such as sub-category, source, item number, or brand.

Header Row Example

The headers shown below are required.

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|custom_field_1|custom_field_2|custom_field_3|custom_field_4|custom_field_5|custom_field_6|custom_field_7|custom_field_8|custom_field_9|custom_field_10

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||275463

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

Send Conversion Data to LiveRamp

If you’re not currently using other LiveRamp Conversions API programs, we might need you to send us sample conversion data to set up the integration.

Once your campaign has started, send conversion data to LiveRamp at your preferred cadence. Files can be delivered at any cadence (preferably daily or weekly).

Tip

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

Caution

Most platforms require that at least 1,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

  • Order ID

Note

The ten "custom_field_" columns must be included, however you do not have to includes values for those columns.

Other optional conversion data (such as event source or store number) can be included as well. See the “Format the File” section below for more information.

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 the this program cannot be uploaded via Connect. We recommend either uploading via our SFTP server, or having us pull files from an S3 bucket or GCS bucket.

After uploading, contact your Customer Implementation specialist to confirm that you have uploaded conversion data. The Customer Implementation specialist will ensure that the file is processed, and will instruct you where to upload future files.

Note

For future uploads, you do not have to email LiveRamp to confirm that you have uploaded data assuming headers have not changed or additional columns have not been added.

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

Most customers automate this process to send files on a regular cadence. Confirm your upload cadence with your Customer Implementation specialist.

FAQs

At what cadence should I send my conversion data files?

LiveRamp can receive conversion data files for this conversions program on a daily, weekly, or monthly basis, but we highly suggest automated daily delivery as it gives LiveRamp the greatest ability to match. If you prefer not to send daily files, the next best option is weekly delivery as this enables data to be reported within the same month.

What conversion data should I include in my conversion data file?

Include all traceable offline transactions in your delivery. Do not include transactions with a transaction date in the future.

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

Do not include transactions with a transaction date in the future.

How long until will it take after I upload my data before I can request a report from Nextdoor?

It usually takes 1-3 days to get the data to Nextdoor. Please work with your Nextdoor account manager for specifics.

In this section: