Skip to main content
Rakuten
Rakuten is configured as an attribution-only integration in OneView. OneView tracks Rakuten touchpoints for attribution and includes them in merit-based routing decisions, but does not send conversion data back to Rakuten's API.
No conversion data is sent back to Rakuten. If you need conversion data sent to Rakuten for campaign optimization, use Rakuten's native tracking or request a full Conversion API integration.

Merit-Based Routing

When Rakuten touchpoints overlap with Conversion API platforms (like Google Ads or Meta), merit-based routing determines which platform receives the conversion based on your attribution model and conversion merit. If Rakuten wins attribution, the conversion is recorded in OneView but not sent anywhere.

Setup

Configure UTM parameters in your Rakuten campaigns with utm_source identifying the platform. OneView automatically captures UTM parameters from all traffic sources—no additional configuration needed.
When overlapping conversions occur, merit-based routing evaluates all touchpoints, including attribution-only platforms:
  1. OneView collects touchpoints from all sources (Rakuten via UTM, Conversion API platforms via click identifiers)
  2. Your attribution model determines which touchpoint gets credit
  3. If the winner is a Conversion API platform (e.g., Google Ads, Meta), OneView sends the conversion to that platform's API
  4. If the winner is attribution-only (e.g., Rakuten), the conversion is recorded in OneView but not sent anywhere
  5. Rakuten remains visible in reports showing it was part of the customer journey

Next Steps

Learn about merit-based routing

Understand how OneView routes overlapping conversions based on attribution merit.

Learn about conversions

Understand how OneView processes conversions across platforms.