E-COMMERCE ANALYTICS · Eコマース アナリティクス

Japanese e-commerce analytics needs Yahoo Japan Shopping conversion tracking set up alongside Google Analytics — and most DTC Shopify stores in Japan are only measuring Google

GA4 captures Google-originated traffic well. It does not capture Yahoo Japan Ads performance, Rakuten referral attribution, or LINE-driven sessions in any meaningful way out of the box. For a Japanese DTC brand, this means a significant portion of the acquisition picture is either missing or misattributed. Yahoo Japan holds a meaningful share of Japanese search volume and display inventory — running campaigns there without conversion tracking is spending without measurement.

Request an Analytics Audit → View the evidence →
This is for you if

Who This Is For

DTC brands operating a Shopify store in Japan and running paid media across both Google Ads and Yahoo Japan Ads, where the analytics setup only reflects one of those two channels.

What's broken

The Problems We Fix

No Yahoo Japan Ads conversion tracking

Brands running Yahoo Japan Display Ads and Shopping Ads without a Yahoo Japan conversion tag have no ROAS data for the Yahoo channel. Campaign performance is measured only by clicks. The Yahoo Japan Tag must be installed via GTM with purchase and add-to-cart event triggers matching the Shopify checkout flow, and Yahoo Japan Ads must be configured to import those conversion events as campaign-level ROAS data.

GA4 sessions from Rakuten referrals attributed incorrectly

When a buyer clicks from Rakuten to the DTC Shopify store, GA4 treats Rakuten.co.jp as the referral source and starts a new session, overwriting the original acquisition channel that brought the buyer to Rakuten. The result is that paid search or display spend that drove the original Rakuten discovery is not credited in GA4. Rakuten.co.jp and its subdomains should be added to the GA4 referral exclusion list so that Rakuten click-throughs do not create a session restart.

LINE share traffic not attributed

Buyers sharing product links on LINE and friends clicking through from LINE appear as direct traffic in GA4 because LINE's in-app browser does not pass referrer information. LINE-driven traffic volume is consistently understated in standard GA4 acquisition reports. The correct fix is adding UTM parameters to all links shared through LINE Official Account campaigns, and educating the marketing team on consistent UTM tagging for any LINE broadcast message.

Japanese privacy law (APPI) not reflected in consent configuration

Japan's Act on the Protection of Personal Information requires that the purposes for which personal information is used are disclosed to users at the time of collection. Deploying GA4 without a Japanese-language privacy policy that describes analytics data use, or without a consent notice for Japanese-language visitors, creates a disclosure gap under APPI. While APPI's consent standard differs from GDPR's opt-in requirement, disclosure of purposes is mandatory and must be reflected in the privacy policy and the analytics data collection notice visible to Japanese visitors.

What we engineer

What We Build

Yahoo Japan Tag installation

Yahoo Japan Tag installation via GTM with purchase, add-to-cart, and checkout event mapping for Shopify

GA4 referral exclusion configuration

GA4 referral exclusion configuration for Rakuten.co.jp and related Rakuten domains

UTM parameter framework for LINE

UTM parameter framework for LINE Official Account broadcasts and LINE-shared product links

APPI-aligned privacy policy review

APPI-aligned privacy policy review and Japanese-language consent notice for GA4 data collection

Looker Studio report

Looker Studio report combining GA4 (Google channels) and Yahoo Japan Ads data into a single acquisition and ROAS view

Conversion tracking health check

Conversion tracking health check covering GA4, Yahoo Japan Tag, and Shopify order event parity

Request an Analytics Audit →
What changes

What you can measure after the analytics infrastructure is in place

Before
After
Before Purchase, add-to-cart, and checkout events are not firing in GA4. Campaign performance cannot be measured against revenue. There is no way to identify which product pages are converting and which are not. Shopify's built-in analytics records that a sale happened but does not tell you which Google or Meta campaign produced it, which keyword the buyer searched, or which product page they landed on before purchasing. Without GA4 e-commerce events configured through Google Tag Manager, your paid campaigns are running blind.
After GA4 shows revenue by acquisition channel — organic search, paid Google, paid Meta, direct, and email are separated into distinct channel groups with revenue attributed to each
Before The Shopify Meta Pixel integration and a manually added Pixel code are both firing on the order confirmation page. Meta is reporting double the actual purchase volume, which inflates your ROAS. This is a common error on Shopify stores that installed the Meta Pixel through Shopify's native integration and then added a second Pixel code snippet directly to the theme. Both tags fire on the thank-you page and Meta counts two purchase events for one transaction. The result is that your Meta dashboard shows a ROAS that is mathematically impossible to reconcile with Shopify revenue.
After Meta purchase events are deduplicated — one purchase in Shopify equals one purchase event in Meta; ROAS calculations are based on actual transaction volume, not inflated event counts
Before Buyers who pay through eSewa or Khalti are redirected away from your Shopify store to an external payment page, then returned to the order confirmation page. The GA4 purchase event on the confirmation page fires correctly for buyers who return through the standard redirect URL. Buyers who use a different return path — or whose browser blocks the event after the redirect — are not measured. This creates a domestic revenue gap in your GA4 data: eSewa and Khalti transactions appear at a lower volume than they actually occur.
After eSewa and Khalti transactions are measured — domestic payment completions are captured in GA4 at the highest rate the payment redirect path allows
Before Klaviyo is sending email and flow campaigns with no click tracking enabled. Email-attributed revenue is not visible in Klaviyo reports. The relationship between lifecycle email sends — welcome flows, abandoned cart sequences, post-purchase campaigns — and actual Shopify revenue is not measurable. You cannot tell whether your email list is driving repeat purchases or whether those buyers were returning regardless of the emails.
After Klaviyo email revenue is visible — each email campaign and flow shows attributed Shopify revenue, click rate, and revenue per recipient
How it works

How the analytics engagement works

  1. 01

    Audit

    Days 1-3

    We review your current GA4 property, GTM container, Meta Pixel, and Klaviyo account. We document every tracking gap, every duplicate event, and every configuration error in a written audit report. You receive the report before any implementation begins.

  2. 02

    Implementation plan review

    Day 4

    We walk through the audit findings and the proposed implementation plan. You confirm the scope before work starts.

  3. 03

    GTM configuration and GA4 e-commerce setup

    Days 5-8

    We build the GTM container with the GA4 e-commerce event layer, the Meta Pixel tag, and the Conversions API configuration. We test each event using GTM Preview mode and GA4 DebugView before publishing.

  4. 04

    Payment gateway testing

    Days 8-10

    We run test transactions through eSewa and Khalti to verify the GA4 purchase event fires correctly after the payment redirect. We document any gaps in the post-redirect firing and implement the best available workaround.

  5. 05

    Klaviyo configuration and handover

    Days 10-12

    We configure UTM tracking on Klaviyo links, verify revenue attribution is active, and deliver a handover document covering every tag, trigger, and variable in the GTM container.

Request an Analytics Audit →
Common questions

Frequently Asked Questions

How do I set up Yahoo Japan Ads conversion tracking for a Shopify store?

Yahoo Japan Ads conversion tracking uses the Yahoo Japan Tag (a JavaScript snippet installed via GTM). On Shopify, the tag fires on the order confirmation page (`/thank_you`) using GTM's purchase event trigger. The conversion event must match the purchase event configuration in Yahoo Japan Ads Manager, and the tag must pass the order value and currency. After setup, Yahoo Japan Ads reports ROAS data at the campaign level once sufficient conversion volume is recorded.

How do I correctly attribute Rakuten referral sessions in GA4?

In GA4, navigate to Admin > Data Streams > select your web stream > Configure tag settings > List unwanted referrals. Add `rakuten.co.jp` and any Rakuten subdomain you observe in your referral reports. This prevents GA4 from treating a Rakuten click-through as a new session source, preserving the original acquisition channel for the buyer's session. The referral exclusion does not remove Rakuten from your reports — it prevents Rakuten from overwriting an earlier channel attribution.

How do I track LINE-driven traffic in GA4 for a Japanese Shopify store?

UTM parameters appended to links in LINE Official Account messages are the only reliable way to attribute LINE traffic. Use `utm_source=line`, `utm_medium=social` or `utm_medium=messaging`, and a campaign-specific `utm_campaign` value for each broadcast. For organic LINE shares (user-generated), UTM tracking is not possible — this traffic will continue to appear as direct. Focusing on UTM tagging for official broadcast campaigns gives you a measurable LINE channel in GA4 acquisition reports.

What does Japan's APPI require for GA4 data collection disclosure?

APPI requires that companies collecting personal information disclose the purpose of use at or before the time of collection, or make the purpose publicly known in advance (typically via a privacy policy). GA4 collects identifiers and behavioural data that qualify as personal information under APPI. The privacy policy must describe analytics data collection, the purpose (e.g., measuring website performance and advertising effectiveness), and the data retention period. A Japanese-language version of the privacy policy is required for Japanese-language sites.

How do I build a Looker Studio report that combines Google and Yahoo Japan performance data?

Yahoo Japan Ads does not have a native Looker Studio connector. The standard approach is to export Yahoo Japan Ads performance data (impressions, clicks, cost, conversions, ROAS) via the Yahoo Japan Ads API into a Google Sheets connector that Looker Studio reads. GA4 data connects via the native GA4 Looker Studio connector. Both data sources are blended in Looker Studio using date as the join key, and channel-level performance is compared in a single table or time-series chart.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

Request an Analytics Audit

DTC brands operating a Shopify store in Japan and running paid media across both Google Ads and Yahoo Japan Ads, where the analytics setup only reflects one of those two channels.

Request an Analytics Audit →