Shopping Portal Authentication Guide

for wildfire white label partners overview authentication is a critical part of powering the shopping experience we provide it allows wildfire to accurately track user shopping behavior, attribute purchases, and—depending on the implementation—enable wildfire to support displaying cash back earnings and facilitating payouts this guide outlines the authentication options available and how each impacts data flow, user experience, and implementation responsibility authentication enables us to identify users during their shopping journey pass identifying info into affiliate links to merchants receive purcha se confirmation from se confirmation from merchants containing that identifying info display earnings dashboard and facilitate payouts via gift card when applicable there are three main authentication options depending on your organization’s needs and technical capabilities 🔧 authentication methods 1\ turnkey authentication (wildfire managed) in this configuration, wildfire handles the entire authentication process using trusted providers (e g , google or apple) no technical work is required from the partner user auth google/apple login powered by wildfire earnings dashboard provided by wildfire payouts managed by wildfire via gift cards ideal for partners without a login system or who prefer a hands off solution key benefits fastest time to market minimal integration overhead fully managed user experience note partners will be unable to tie user purchases to user profiles (i e partner will be unable to use purchase data for marketing/crm purposes or otherwise) 2\ tracking id pass through (partner managed lightweight auth) this method allows a partner to pass an anonymous user id (such as a uuid or internal analytics reference) into the shopping portal via url parameters wildfire captures and persists this id through the user’s shopping journey, enabling attribution of purchases user auth partner controlled (via id passed in url) earnings dashboard / payouts owned by partner ideal for partners who facilitate payouts, want a lightweight solution and ability to tie purchase behavior with user profiles example flow user starts on partner site partner appe nds a unique id in t nds a unique id in t he url when directing the user to the shopping portal wildfire includes this id in affiliate link parameters purchase data with this id is returned to the partner via reporting key benefits simple integration partner can tie user purchases to user profiles (i e partner will be to use purchase data for marketing/crm purposes or otherwise) example url shoppingportal site com?uuid=uuidhere 3\ oauth integration (partner managed secure auth) wildfire supports integrating with your oauth 2 0 based authentication system for a secure, seamless user experience this allows for deeper user level attribution and flexible options for managing earnings user auth partner oauth earnings dashboard / payouts can be wildfire or partner owned ideal for partners with an existing secure login system and interest in richer data access or payout flexibility options partner managed dashboard and payouts wildfire managed dashboard and payouts (only available via oauth or turnkey solution) implementation notes each oauth implementation is customized to the partner's infrastructure requires technical alignment and partner provided documentation please coordinate with your wildfire customer success representative to begin technical planning key benefits secure user authentication allows flexible ownership of payout and user engagement components partner can tie user purchases to user profiles (i e partner will be to use purchase data for marketing/crm purposes or otherwise) 🔁 summary comparison feature turnkey auth tracking id pass through oauth integration partner owns auth ❌ ✅ ✅ wildfire manages payouts ✅ ❌ ✅ (optional) wildfire provides dashboard ✅ ❌ ✅ (optional) integration effort minimal low moderate partner can associate purchases with users ❌ ✅ ✅ authentication for app only partners for partners that operate exclusively within a mobile app and do not support web based logins, authentication should be handled within the app before opening the shopping portal authenticating users via app launch the portal with a user id since the user is already authenticated in the partner’s app, open the portal url with the user’s unique identifier (uuid) appended as a query parameter shoppingportal site com?uuid=uuidhere user tracking the portal will store the uuid and use it as a tracking code for all affiliate link activations this ensures that purchases made through the portal are correctly attributed to the authenticated user handling web links when only app based logins are supported if the app based partner also has a website that links to the shopping portal but does not support web based logins, follow this process redirect to the app for authentication when a user attempts to log in, redirect them to the app using an app deep link (e g , app\ //) instead of a web based login flow (https //) return to the browser with user id once the user is authenticated in the app, redirect them back to the browser with the uuid appended to the url shoppingportal site com?uuid=uuidhere user tracking the portal will store the uuid and use it as a tracking code for all affiliate link activations this ensures that purchases made through the portal are correctly attributed to the authenticated user 📩 getting started to begin setting up authentication, contact your wildfire onboarding representative they will help you choose the most appropriate integration option and provide technical resources and guidance for implementation