Affiliate/Vendor Campaign Tracker MVP

# Affiliate / Vendor Campaign Tracking Platform – MVP **Budget: ₹8,000 – ₹10,000 INR** We are looking for an experienced developer to build an **Affiliate / Vendor Campaign Tracking Platform** for our performance marketing business. The platform will be used to manage clients, campaigns, vendors/publishers, tracking links, conversions, postbacks and campaign performance from one central dashboard. This is **not an influencer marketing platform**. It is primarily an affiliate/performance marketing tracking system. ## Main Requirements ### 1. Admin Dashboard We need a simple and easy-to-use admin dashboard where we can manage: * Clients * Campaigns * Vendors/Publishers * Tracking links * Conversions * Reports * Campaign status * Caps and limits * Revenue and cost * Profit The system should be easy for a non-technical person to operate. ### 2. Client Management Admin should be able to: * Add clients * Edit client information * Store contact details * Store payment terms and currency * Add internal notes * Activate, pause or archive clients * View all campaigns associated with a client * Upload client-related documents if required Each campaign should belong to one client. ### 3. Campaign Management Admin should be able to create campaigns with information such as: * Campaign name * Campaign ID/code * Client * Campaign type * Conversion type * Client payout/CPA * Target GEO * Daily cap * Monthly cap * Start/end date * Campaign status * Client landing/redirect link * Internal campaign notes Campaigns should support statuses such as: * Draft * Testing * Live * Paused * Completed * Archived We should be able to pause or resume a campaign at any time. ### 4. Vendor / Publisher Management We need to manage multiple vendors/publishers. For each vendor we should be able to store: * Company name * Contact person * Email * Phone * Telegram/Skype * Country * Payment terms * Currency * Traffic type * Vendor status * Postback URL * Internal notes Vendor statuses should include: * Pending * Approved * Suspended * Blacklisted ### 5. Assign Multiple Vendors to a Campaign A single campaign should be able to have multiple vendors. Each vendor can have different: * CPA/payout * Daily cap * Monthly cap * Tracking link * Postback URL * Status * Internal notes For example: * Vendor A → $1.20 * Vendor B → $1.50 * Vendor C → $2.00 Adding or removing a vendor from a campaign should **not require any changes from the client**. ### 6. Tracking Links The system must generate a unique tracking link for each vendor/campaign combination. When a visitor clicks the vendor's tracking link: **Vendor → Tracking Link → Generate Click ID → Record Click → Redirect to Client** The system should record the click and generate a unique Click ID. Tracking links should support: * Click ID * Vendor identification * Campaign identification * Sub1 * Sub2 * Sub3 * Sub4 * Sub5 The public tracking URL should not expose sensitive internal IDs unnecessarily. ### 7. Click Tracking For every click, the system should record information such as: * Click ID * Campaign * Vendor * Date/time * IP address * Country * Device * Browser * Operating system * User agent * Referrer * Sub1–Sub5 This information should be available for reporting and traffic-quality analysis. ### 8. S2S Postback / Conversion Tracking This is a **very important requirement**. The platform must support server-to-server conversion tracking. The basic flow should be: **Vendor → Tracking Link → Client → Client Postback → Platform → Conversion → Vendor Postback** The client should only need to integrate with the platform once for a campaign. The system should support postback parameters such as: * Click ID * Conversion status * Transaction ID * Sale amount * Currency * Payout * Sub1–Sub5 The platform must match the incoming conversion with the correct click and vendor. ### 9. Duplicate Conversion Protection The system must prevent the same click from being counted more than once. Duplicate conversions should be identified and recorded separately rather than incorrectly increasing the campaign's conversion count. ### 10. Conversion Management Admin should be able to view conversions and their status. Conversion statuses should include: * Pending * Approved * Rejected * Duplicate Admin should also be able to manually approve or reject conversions when necessary. Manual changes should be recorded for future reference. ### 11. Postback Logs The system should maintain logs for: * Incoming client postbacks * Outgoing vendor postbacks * Successful postbacks * Failed postbacks * Duplicate postbacks Admin should be able to review the postback request and response details. A failed postback should be capable of being resent manually. ### 12. Campaign & Vendor Pause Admin should be able to: * Pause/resume an entire campaign * Pause/resume an individual vendor * Pause all vendors under a campaign If a campaign or vendor is paused, new traffic should not be counted as valid traffic/conversions. Blocked traffic should still be logged. ### 13. Daily & Monthly Caps The platform should support: **Campaign-level caps** * Daily cap * Monthly cap **Vendor-level caps** * Daily cap * Monthly cap When the cap is reached, the campaign/vendor should automatically stop accepting traffic. ### 14. Revenue, Cost & Profit The system should calculate: * Client revenue * Vendor cost * Profit * Profit percentage * Conversion rate * ROI For example: **Revenue = Approved Conversions × Client CPA** **Cost = Approved Conversions × Vendor CPA** **Profit = Revenue − Cost** We should be able to see these figures by campaign and vendor. ### 15. Reporting The dashboard should provide reports for: * Campaign performance * Vendor performance * Client performance * Daily conversions * Country performance * Device performance * SubID performance * Revenue * Cost * Profit * Approved conversions * Rejected conversions * Duplicate conversions * Postback