How Sure Imports Affiliate Tracking and Attribution Work
Understand Sure Imports affiliate tracking, referral ownership, API-created shipping requests, qualifying events and how to protect attribution.
Tochukwu Nkwocha
Founder
Affiliate tracking and attribution answer two different questions: what interaction was recorded, and which affiliate owns an eligible commercial outcome. For Sure Imports, a visit is not the final outcome. Attribution must connect a partner’s introduction to the relevant paid service event.
Understanding that chain helps affiliates troubleshoot responsibly. It also prevents the common mistake of treating every click, request estimate or customer registration as earned commission.
The attribution chain
- The affiliate selects the correct service link or approved API workflow.
- A customer uses that route and the platform records the relevant referral context.
- The customer starts the intended service journey.
- A qualifying payment or fully paid linked invoice occurs.
- The system applies the configured commission basis and creates a snapshot.
- The commission passes through the review workflow before becoming available.
Why a click is not a commission
Clicks reveal interest, but some visitors are researching, some abandon the process and some choose an ineligible service. Commission exists only after the configured business outcome. That design aligns the programme with delivered customer value rather than raw advertising volume.
Use click and visit data to improve content, but use attributed eligible transactions to evaluate commercial performance. A page with fewer visitors can be more valuable if it answers a high-intent question precisely.
Service-specific qualifying events
Buy From Chinese Websites uses eligible product cost. Supplier Reports, Phones and Laptops, and Supplier Verification use fixed eligible transactions. Supplier Intelligence uses qualifying subscription payments. Ship with Us waits for the linked invoice to be fully paid and uses final eligible billed quantity.
These distinctions explain why two referrals that begin on the same day may appear in different stages. One might be awaiting payment, another under review and another available.
API request ownership
When an authorised affiliate API key creates a shipping request and the API accepts it, that affiliate owns the request. The creation response includes attribution details and a lock time. Retries with the same idempotency key should resolve to the same logical creation instead of producing competing requests.
Request ownership is deliberately narrower than the customer’s general relationship. It does not rewrite attribution for unrelated services or future journeys. This gives business integrations certainty about requests they originate without claiming every action that customer may ever take.
How to reduce lost or disputed attribution
- Use the service link copied from your authenticated dashboard, not a manually edited approximation.
- Test the link in a clean browser and confirm that it reaches the intended service journey.
- Do not place another partner’s tracking parameters inside your content.
- For API requests, retain the external reference, idempotency key and returned request ID.
- Do not ask customers to create duplicates when a request already exists.
- Raise a support query with specific references and timestamps, never with an unsupported earnings estimate.
Privacy-aware measurement
Attribution does not justify collecting more personal data than necessary. Dashboard reports can identify operational outcomes while masking customer details where appropriate. Affiliates should protect exports and avoid sharing customer records in public communities.
For content analytics, track aggregate landing-page and conversion patterns. For transaction support, use the identifiers supplied by the platform. This separation keeps marketing analysis useful without turning customer data into promotional material.
A practical reconciliation routine
Once a week, compare your published service links, attributed requests, commission statuses and completed payouts. Annotate campaigns with dates and topics so you can explain changes. For API integrations, reconcile your external reference against the Sure Imports request ID.
If traffic rises but attributed requests do not, inspect link placement and intent. If requests rise but eligible payments do not, improve qualification and explain the service more accurately. If a status changes after payment, check review and reversal information before escalating.
The practical next step
Treat tracking as an evidence chain. Preserve clean links and request identifiers, explain the qualifying event accurately, and reconcile dashboard stages instead of estimating commission from traffic.
Frequently asked questions
Does every tracked visit create commission?
No. A customer must complete the qualifying paid event for an eligible service.
Is an API-created shipping request permanently attributed?
The accepted request has locked affiliate ownership. This request-level ownership does not replace the customer’s general relationship for unrelated journeys.
What should a business store after API creation?
Store its external reference, idempotency key, returned request ID, status and attribution record.
Why can commission change during review?
Refunds, reversals, duplication, eligibility issues or breaches can affect pending commission.
How do I troubleshoot attribution?
Verify the exact link or API identifiers, note timestamps and service route, then use those records when contacting support.
Ready to build a commission channel around real import and shipping needs? Create a free Sure Imports affiliate account, review the affiliate terms, and use the current service links and commission rules shown in your dashboard.
