Rakuten Conversions

Send conversion and transaction data to Rakuten Advertising server-to-server for affiliate attribution, publisher commissions, and campaign analytics.

⚠️

This blueprint is currently alpha — schema and behaviour may change before GA.

Prerequisites

Complete these steps in the Rakuten Advertising dashboard before configuring Signal.

Create a Rakuten Advertising account

Find your Advertiser ID

Navigate to Account > Account Summary in the Rakuten dashboard. Your Advertiser ID is displayed in the account details section. This identifies your advertiser programme.

Find your Merchant ID (MID)

Your Merchant ID (MID) is shown alongside your Advertiser ID in the account details. In some Rakuten interfaces, it appears under Account > Tracking Settings or is provided by your Rakuten account manager.

Generate an API key

Go to Account > API Access (or Tools > API Credentials) in the Rakuten dashboard. Generate or copy your API Key. This key authenticates server-to-server conversion tracking calls.

Configure commission structures

Navigate to Offers > Commission and ensure your commission structures are defined. Server-tracked conversions will be attributed using these commission rules, so they must be in place before sending events.

Verify tracking link parameters

Ensure your Rakuten affiliate links include the standard tracking parameters. Server-to-server conversions require a valid click reference (typically the ranMID, ranEAID, and ranSiteID parameters) for attribution.

Configuration

Field	Type	Required	Description
`advertiser_id`	string	Yes	Your Rakuten Advertising advertiser ID.
`api_key`	secret	Yes	Your Rakuten API key for authenticating server-to-server calls.
`mid`	string	Yes	The Rakuten merchant ID (MID) associated with your advertiser account.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Rakuten Conversions or filter by Attribution.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/rakuten/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Rakuten Conversions",
    "variant": "default",
    "config": {
      "advertiser_id": "12345",
      "api_key": "your_api_key",
      "mid": "67890"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The Retail variant maps the following Datafly events to Rakuten conversion events:

Datafly Event	Rakuten Event	Notes
`Product Added`	`add_to_cart`	Cart-stage event
`Order Completed`	`purchase`	Requires `orderId`, `amount`, `currency`, `mid`
Custom events	Passed through	Add the Rakuten conversion type in the blueprint event map

Identity

The default blueprint forwards the following identifiers to Rakuten:

Source	Rakuten field
`user_id`	`customer_id`
`context.ip`	`ip_address`
`context.user_agent`	`user_agent`

Rakuten’s ranSiteID and ranEAID click parameters are the primary attribution tokens. Capture them from inbound URLs on your landing page and pass them via Datafly.js so they reach Rakuten with each conversion.

Default consent category: advertising.

Rakuten requires the ranSiteID (publisher site ID) and click tracking parameters to attribute conversions to the correct publisher. Ensure your site captures these values from landing page URLs and includes them in Signal events.

Verify it’s working

Generate a test click through a Rakuten affiliate tracking link.
Complete a test conversion on your site that triggers a Datafly event.
In the Signal Management UI, open your Rakuten integration and watch the Live Events stream.
In the Rakuten dashboard, navigate to Reports > Transaction Detail to verify the test conversion (allow up to 30 minutes for processing).
Confirm 200 responses in Signal’s Live Events log.

Troubleshooting

Symptom	Cause	Resolution
`401 Unauthorized`	Invalid API key	Verify `api_key` in Rakuten Account > API Access and update Signal.
`400 Bad Request`	Missing required fields	Ensure `orderId`, `amount`, and `mid` are mapped in the blueprint.
Conversions not appearing	Missing click tracking parameters	Rakuten tracking parameters (`ranSiteID`, etc.) must be captured and forwarded.
Wrong merchant	Incorrect `mid`	Verify the Merchant ID matches your advertiser account in Rakuten.
Commission not calculated	Commission structure not configured	Set up commission structures in Offers > Commission before sending conversions.

Visit Rakuten Advertising documentation for full API reference and credential setup instructions.

Blueprint

The Rakuten blueprint version is 0.1.0 (alpha). It ships with a Retail variant covering add_to_cart and purchase conversion events.