Call Brief · Partner Nook × Trackier

How to explain the product & what to ask on the Trackier call

Partner Nook is Trackier's own Shopify product — so this is an internal alignment call. Show the team what's built, agree how it maps to the Trackier API, and walk away with API access & the exact endpoints.

🗣️ Kaise use karein: upar se neeche padho. Section 1–2 bolne ke liye hai (product + architecture samjhana), Section 3 dikhata hai aapne unke model ko samajh liya hai, Section 4 me sawaal poochne hain, Section 5 = call se kya leke nikalna hai. English lines aap seedha bol sakte ho.

01 Open with the 30-second pitch

Everyone's on the same team — frame it as "here's the Shopify layer we built on our own Trackier infra, help me use the API right."

Say this

"Partner Nook is our Shopify app that lets D2C brands run an affiliate & influencer program from inside Shopify — a lightweight, brand-native product built on top of Trackier's API. Merchants manage affiliates, commissions, coupons and payouts; affiliates get a self-serve portal."

"The app layer is done. Now I want to wire the tracking into Trackier — creating publishers & tracking links, recording clicks and conversions, and pulling stats — instead of the coupon-only tracking we have today. I need to confirm the right endpoints and get API access for the app."

Because it's internal: API access should be quick to get — the real value of the call is agreeing the data model (advertiser/campaign per merchant, publisher per affiliate) and the exact conversion/postback flow.

02 Explain what's already built

Be honest and concrete — it builds credibility and helps them slot their API in.

Say this

"The app is built and working: a NestJS + Postgres backend and a Next.js portal. Today, attribution runs on Shopify coupon codes + order data — an affiliate's code is used at checkout, we read the order via Shopify's Admin API and calculate commission."

"That covers coupon-based sales. What we need Trackier for is the link/click side and a single source of truth for tracking — recording clicks on referral links, recording conversions, and reporting. Our data model already has placeholder fields — trackierId on each affiliate and trackierClickId on each click — ready to wire."

Ek line me: "Coupon tracking humare paas hai; link tracking + unified reporting ke liye Trackier chahiye."

03 Concept mapping — speak their language

Show this table (or say it). It proves you understand Trackier's model: advertisers, campaigns, publishers, tracking links, conversions.

Partner NookTrackier (their term)What happens
Merchant (the brand)→Advertiser + Campaign / Offereach store = one advertiser/campaign with payout terms
Affiliate→Publisher / Partnercreated via API on approval → we store trackierId
Referral link→Tracking link (click URL)generated per publisher per campaign
Click→Clickrecorded on the tracking domain → we keep trackierClickId
Order (Shopify)→Conversion / Goalwe send a server-to-server postback with click id + amount
Dashboard stats→Reporting APIclicks / conversions / revenue per publisher
Confirm this mapping with them first — "Is this how you'd model a Shopify affiliate app on Trackier?" Their answer shapes everything else.

04 Questions to ask — grouped

Cover access, each of the four jobs, testing, and commercials. Tick them off during the call.

1 Access & authentication

  • What's the API base URL and auth method (API key header? OAuth token)?
  • Is there a sandbox / test environment so we can integrate without live data?
  • Where's the API documentation?

2 Publishers & tracking links

  • Can we create publishers programmatically (one per affiliate, on approval)?
  • Can we generate a tracking link per publisher per campaign via API?
  • Do links support sub-IDs / custom params so we can carry our affiliate id or coupon code?

3 Clicks & conversions

  • How are clicks recorded — do visitors go through your tracking domain and redirect to the store? Do you return a click id we can store?
  • For conversions, do you recommend server-to-server postback or a pixel for Shopify? (We prefer S2S from our backend.)
  • What's the postback format — required params (click id, sale amount, order id, currency)?
  • How do we dedupe (so one order = one conversion) and handle refunds / reversals — is there a reversal API?

4 Reporting

  • Is there a Reporting/Stats API for clicks, conversions and revenue per publisher, by date range?
  • What's the data freshness (real-time vs delayed)?

5 Practical & ops (internal)

  • Which Trackier account / workspace should the app use, and how do we provision one advertiser/campaign per merchant as brands install?
  • Tracking domain setup — custom domain per brand or a shared one?
  • Rate limits / bulk endpoints — the app will create many publishers & fire many conversions.
  • Any existing Shopify integration, SDK, or internal docs we should reuse instead of rebuilding?

05 What to walk away with

Don't end the call without these — otherwise the build stays blocked.

✅ Leave-with checklist

  • API key + secret (sandbox at minimum)
  • Link to the API documentation
  • Confirmed mapping — advertiser/campaign per merchant, publisher per affiliate
  • The conversion method — postback URL format + exact required params
  • Tracking domain instructions
  • Ideally a worked example: create a publisher → get a tracking link → fire a test conversion → see it in a report
  • Which account/workspace the app should use + how new brands get provisioned
After the call: in bao mujhe do (API docs + key), aur main poora TrackierService (createPublisher · createTrackingLink · postConversion · getStats) bana ke approval + click + conversion + stats wire kar dunga.