---
# System prepended metadata

title: Project R Plan

---

# Project R Plan

## Important Processes
### Onboarding
- Creating a Campaign
    - Choose what fields will be captured for the referral (ie first name, last name, etc)
	- Choose the destination URL
	- Will the payout be Flat or Dynamic?
	    - Dynamic would be for variable deal sizes where you get paid a percentage.
- Onboarding a Partner
    - When a partner signs up (and gets approved), send a welcome email that contains the shareable "shortened" tracking URL
- Setting up an integration
    - At this point, I don't know how this could be accomplished without an advanced connection using APIs. I think we need to provide both direct integrations (as they are built) as well as a simplified API for setting up custom integrations (see API section below)


## Important Elements:
### Campaigns
- Landing Page URL(s)
- Some sort of deep-linking mechanism
- Some way to direct Mobile vs. Desktop traffic to different landing pages
- Associated with a list of statuses for the lead
- Associated with specific data fields for a referral
### Partners
- need to be able to login to partner portal (so need Username and Password)
- basic company information
- ALLOW partners to manage / see data for other partners??
	- breakaway movement wants this as well as other clients. they have team leads and some have parent companies that manage child companies
### Referrals
- Each referral comes through a partner (associated with a partner)
- Each Referral has a status
- Each referral would have different collected data fields depending on the campaign
### Statuses
- If we are allowing multiple campaigns, we should allow for multiple sets of statuses to be used in different campaigns (though this doesn't necessarily mean this should be visible to the user). 
    - One status list per campaign
### Promo Codes
- The way I see it, promo codes would be associated with a campaign-partner combination.
- they should be able to be used in an API integration
### Affiliate Payments
- Something to note is that some partners don't want to pay out to their partners using real money. A lot of the time they want to have some custom rewards system, such as a gift card to their platform, or some sort of in-platform currency.
### Partner Portal
- Allow partners to log in and see their referrals
- Give partners their URL
- If we decide: allow partners to also access the referrals of other partners that they are allowed to manage (hopefully in a one-by-one and all-at-once fashion)
- ARE WE GOING TO ALLOW WHITE LABELING? 
    - if so, is it full white labeling? or just like a Logo and coloring (which would probably be easier)?

### APIs (must-have for integrations)
- Be able to list all partners, create new partner
- Pull partner referrals
- Update a referral status (or possibly other information on a referral)
#### Unathenticated API
- One important element with LinkTrust is we essentially have an unathenticated API used for pixel fires. It is important that we make this available for referrals since many systems are limited in capability and won't always be able to perform the necessary authentication methods
## Business Differences between Project R and LinkTrust:
- Simplified experience (and functionality)
- Single campaign (maybe 2)
- Not as much tracking conversions, need to track the status of the lead