Welcome!
Welcome to the Marin Software Support Center. We're glad you're here. Here's what you can look forward to:
  • Real-time search so you can find what you need faster than ever.
  • Easy-to-follow video guides for our most popular articles.
  • Interactive simulations and Live Screenshots to make learning easy.
  • Regular content updates to ensure every word you read is accurate and up-to-date.

Revenue and Conversion Tracking

Home > English > Revenue and Conversion Tracking > Revenue Upload > Troubleshooting Articles: Revenue Upload > Possible Reasons For Device Data Going to Other

Possible Reasons For Device Data Going to Other

Introduction

When tracking conversions tagged with device, you may find that device data is tracked 'other'. There are multiple reasons why device data might go to other. In this article, you review some of the most common reasons.

Latent Conversions

Latent conversions might cause data attributed to other instead of a device, as the initial click might not have included {device}. This will typically impact you, if you are using Date of Conversion Tracking.

Tracking IDs Section not configured correctly for a uRL format

To ensure your Tracking IDs are configured correctly, follow these steps:

  1. Click the Admin link in the upper-right.
  2. Select the Revenue sub-tab.
  3. Click Tracking IDs in the left-hand menu.

Using the Combined Approach

Example of combined URL:

http://www.example.com?mkwid=[uniq_id]_d[device]&pcrid=[creative]

The Device type appended? box needs to be checked off, and the Device delimiter needs to be set as Underscore ('_').

Possible values are Underscore ('_'), Pipe ('|'), and Hyphen ('-').

Using the Separate Approach

Example of separate URL:

http://www.example.com?mkwid=[uniq_id]&pcrid={creative}&pdv={device}

If you use the Platform Tracker, you need to have the {Device} Parameter tab filled out. In this above example, the Parameter Name is 'pdv', the Value Separator is the Equals Sign ('=') and the Stop Character can be set as Ampersand ('&').

URL Builder not set up to include device

If you use URL Builder, make sure the {device} parameter is included, so new URLs will be built with it included. Be sure to also check Product Target URL builder, as well as folder-level URL Builder, if it applies.

Keywords on Google or Yahoo! Japan do not have {device}

Use grid filters to identify keywords not tagged with {device}. Filters might include Destination URL does not contain pdv={device}, _d{device}, -d{device}, or |d{device}.

Sitelinks not tagged with {device}

Depending on the method used for tracking sitelinks, as well as the method used for tracking device, you may need to update your Sitelink URLs directly in AdWords. For enhanced Sitelinks, you will need to verify, if they are tagged with {device} in AdWords, since we do not currently sync enhanced ad extensions into the Platform.

Product Targets

Google is experiencing an error on their end in which they do not consistently populate {device} on PLAs (Product Listing Ads) even if the {device} parameter is in the URL. One possible work around to receive this data is to copy the PLA URLs to the adwords_redirect field in Google Merchant Center.

Using other revenue sources (including FTP)

If you are using other revenue sources, such as FTP, you will need to ensure that the Device parameter is appended to the keyword ID, or provided in its own Device column. Otherwise, the data may appear in Other.

Creative not tagged with {device}

You are doing creative level tracking or A/B test, and creative is not tagged with {device}.

Last modified

Tags

Classifications

This page has no classifications.

 

wiki.page("Internal/Mindtouch_Launch_Sandbox/js.cookie.js")