Today this table contains data from Superfiliate and ShopMy. Support for additional affiliate platforms is on the roadmap. If there is a platform you would like us to integrate with, reach out to your Customer Solutions Engineer.
When to use this table
Useobt_affiliate_conversions when you need affiliate or creator activity at the level of individual orders. Each row is one conversion, which for every current platform is one order.
This table replaces rpt_affiliate_performance_daily, which summarized to a daily total per affiliate and in doing so dropped the order identity. Because this table carries sm_order_key, affiliate activity now joins directly to the rest of your warehouse.
Common questions this table can answer:
- Which specific orders did a creator or affiliate drive?
- What did those customers actually buy, by joining through to order lines?
- Which affiliates bring in first-time customers rather than repeat buyers?
- What is the true commission rate for a period, affiliate, or campaign?
- How long after a creator link click did the order happen? (ShopMy)
Rebuilding the daily affiliate report
Everything the retiredrpt_affiliate_performance_daily showed is one aggregation over this table:
Common joins
- Join to
obt_ordersonsm_order_keyfor full order detail, channel, and customer attributes. - Join to
obt_order_linesonsm_order_keyto see what products an affiliate order contained. - Compare against
rpt_ad_performance_dailyon(date, source_system)for cross-channel spend comparison. Affiliate commission appears there as spend.
sm_order_key is NULL when a conversion could not be matched to an order. Read it together with is_new_customer: on an unmatched row, is_new_customer falls back to TRUE rather than being derived, so a NULL key means “assumed new”, not “confirmed new”. Filter on sm_order_key IS NOT NULL when you need only confirmed matches.
