Ember
🔍 Entity · Org / brand

Trip.com

16 mentions across 3 BUs — 9 facts, 7 signals.

Where this org / brand shows up

BU breakdown of mentions

  • iAds10 mentions
  • Enterprise5 mentions
  • Subscriptions1 mention

Mention timeline

Every fact and signal naming Trip.com, newest first

  • signal
    iAds
    Trip.com is one counterparty fragmenting across three BU workstreams
    Three independent Trip.com problems are running in parallel across three BUs with no unified account view — Trip will see one stressed partner relationship, IA is managing three disconnected tickets. — Trip just named IA #1 partner. The next escalation call lands without a single account narrative — Andrew Tay, Sam Yap, and Lindsay are each holding a third of the picture.
  • signal
    iAds
    Publisher traffic-quality enforcement applied asymmetrically — same fault pattern, different consequences
    Three named publisher operations are exhibiting the same failure shape (clicks without legitimate conversions / WoW violations), but only one was suspended. The intervention bar appears to be reputation, not behaviour. — Trip.com's commercial side will notice the inconsistency before IA does. If "we suspended Stars" is the answer when Huynh is the new violator, the credibility of the enforcement framework collapses — and Sam Yap's ISP makes the same point internally.
  • signal
    iAds
    Two named iAds publisher failures route directly into Enterprise advertiser exposure
    The iAds zero-conversion period — now diagnosed as Sam Yap's iAds Social Project (3.5k clicks/day, zero conv) and Raja Nazaruddin's iAds Vivo (traffic dead since late April) — is firing on the same Enterprise AG advertiser book that is already absorbing the Trip.com violation reset and the Deepleaper/TikTok Shop ID gap. — AG account managers are absorbing publisher-side failures they didn't cause, on advertisers (Trip, Shein, Klook, TikTok Shop) that will see the reconciliation. Tay's 30%-legitimate-source goal slips further while AG owns the advertiser relationship damage.
  • iAds
    iAds brand mix
    TikTok 43.82% Apr–May contribution, displacing Trip.com as co-leader
  • Subscriptions
    iAds zero-conversion period is NOT validation backlog — diagnosis revised (HISTORICAL — see CORRECTION below)
    **CORRECTION 2026-05-15: "iAds Social Project" has no connection to iAds publisher. See full correction entry below.** Investigation 2026-05-14 BQ deep-dive: the 14-day zero-conversion period across certain publishers (last validated conversion 2026-04-29) is **not** a validation-pipeline collapse. The BUP-1 framing as "validation backlog · realization rate 5.6%" was wrong. The actual story is two distinct operational issues across two publishers: **ISP publisher "iAds Social Project" (aff_id 1008463, Sam Yap-managed, Enterprise PG)** — the dominant click source at ~3.5k/day from May 5 onward. Clicks fire on LIVE converting offers (Shein, Trip.com, Klook, Oppo ID) but produce ZERO conversions. **Smoking gun**: Shein-CPS — ISP sent 4,465 clicks; other publishers run Shein at ~3.15% conversion rate; expected ~140 conversions, actual 0. That's not variance. Almost certainly traffic-quality (bot / incentivised / misattributed audience) OR a tracking/postback misconfiguration specific to this publisher's links. **Sam Yap should be asked to verify ISP's traffic source + check postback URLs.** **iads vivo (aff_id 1065674, Raja Nazaruddin-managed)** — was healthy at 70-370 clicks/day with 1-7 conversions through April. **Late April collapse**: April 29 dropped to 3 clicks; May 1-12 just 1-3 clicks/day. This is a publisher traffic source dying, not a tracking issue. **Raja should check ivans vivo's upstream traffic source.** **Validation pipeline is fine**: in the same 14-day window, the other 88 Raja-managed publishers recorded 821k conversions on 87M clicks. Validation infrastructure is processing normally. iAds-specific zero is a real operational outcome, not a data lag. When the brief next addresses the iAds "validation collapse" item, anchor the diagnosis on these two specific operational issues, not on validation-pipeline framing. The 92.7% deep-critical backlog metric Andrew Tay's sheet shows must mean something different from what BUP-1 inferred — likely an internal iAds-team metric about offer health or postback latency, not BQ aggregate latency.
  • iAds
    Analysis pattern — offer ↔ publisher pairing is mandatory for affiliate-marketing claims
    When the brief makes a claim about an offer-side event (e.g. "Trip.com collapsed", "iAds Stars halt", "Lazada commission cut"), it MUST follow up with the publisher-side impact: - Which publishers were running the affected offer? - Of those, which dropped the most volume / revenue? - Was the drop concentrated in 1-2 publishers (counterparty-specific risk) or systemic across many (structural shift)? The reverse pattern also applies: when a publisher's volume moves, name the offers driving it. This is the analysis lens used in operating reviews — abstracting to "Trip.com is down" without naming the publisher exposure is meaningless.
  • Enterprise
    BQ analysis gap — offer × publisher pairing not yet available
    Current BQ routed metrics are aggregated either offer-side OR publisher-side, not paired: - publisher_concentration → top 10 publishers, revenue-only (no offer breakdown) - iads_revenue → revenue / offer count / publisher count by day (no per-pair detail) - ag_revenue_split → revenue per account manager (no offer breakdown) - offer_health_decay → offers without publisher attribution To answer "Trip.com dropped — which publishers?", a new BQ metric is needed that joins offer × publisher × revenue over time. Until that's built, briefing claims about "which publishers dropped on a specific offer" should be flagged as "publisher-side data unavailable" rather than fabricated.
  • Enterprise
    Investigative-journalist mode for the brief
    Treat each Top 6 item as a story to investigate, not a data point to report. The brief's job is to dig: - When a number looks anomalous → pull the trailing distribution before claiming significance - When an event has a named counterparty → name the publishers / advertisers / deals affected - When a metric moves → propose 2-3 specific hypotheses with evidence from BQ / sheets / Basecamp, NOT generic "undiagnosed" - When relevant external context exists → flag it but do not invent (e.g. "Trip.com's Q1 investor report would tell us whether their HK/KR cut is platform-wide or just IA-specific — worth checking, but not in scope today") - Always ask "what would the team head actually do with this?" — if no answer, the item doesn't belong in Top 6 External-source augmentation is interesting but defer for now (Jim's note: "I'd rather not muddy the waters even more"). Capture as future capability.
  • signal
    iAds
    Trip.com risk is now a three-BU containment failure, not an iAds incident
    What began as a single-partner brand-safety event is now visibly compressing supply (publisher count 11→10), sitting unowned across five Basecamp-silent days, and is dependent on a TikTok validation fix (May 14) that Group Services itself doesn't control. — Enterprise absorbs the revenue (it's the YTD MYR 57.3M buffer being drawn down), iAds absorbs the operational silence, Group Services absorbs the reporting blind spot — but no single BU is structurally accountable for the partner conversation.
  • signal
    iAds
    May demand-side reads are softening in lockstep
    Three independent revenue series are decelerating across the same 5–10 May window, with no shared exogenous explanation beyond Trip.com — suggesting either compounding partner impairment or a broader demand-side softening that no single BU is positioned to diagnose. — If 10 May closes confirm the trend across all three, the question moves from "Trip remediation" to "is May structurally weaker than April." The MYR 57.3M YTD buffer at Enterprise hides this at consolidated level.
  • iAds
    Trip.com iAds Stars
    traffic halted 7 May 2026 after 75% WoW violations spike (77% concentrated on iAds Stars); estimated RM95k revenue loss
  • signal
    iAds
    Brand-safety and compliance items accumulating without escalation owners
    Four live integrity items — each capable of standalone reputational or regulatory consequence — sit unassigned simultaneously, and none has a named escalation route above department. — Compliance and brand-safety risks compound non-linearly; a second viral incident while Trip.com JP is still unscoped converts a partner conversation into a category conversation. The absent escalation path is itself the risk.
  • Enterprise
    Trip.com JP adult-content incident
    04 May 2026 — viral X post tied an IA link to adult content; JC paused JP traffic, Trip upper management engaged, revenue impact unscoped
  • Enterprise
    Trip.com commission
    HK/KR upsize removal extended Hotel-wide and to International Flights, effective May 2026
  • Enterprise
    Trip.com JP
    traffic suspended due to adult-traffic brand-safety escalation; sole owner Lindsay Maralit
  • signal
    iAds
    Trip.com is becoming a portfolio-level exposure with no consolidated owner
    Trip.com is simultaneously a featured iAds spend partner in a week where ROI$ shrank, an Enterprise account losing JP traffic and Hotel-wide upsize commission, and a Group Services line item confirmed live for May — but no single function is reconciling the combined commercial impact. — iAds may be scaling spend into a partner whose monetisation structure is simultaneously deteriorating on the Enterprise side — the BU absorbing the margin hit is iAds, but the decision lever sits with Enterprise.