Back to all workSites3 Source formats4 WorkflowReady
Custom applications
Conversion attribution platform
Connecting clicks and conversions when the data arrives at different times.
Clicks were recorded in one system while conversion information arrived later from several others. We built a central application that brings those records together, handles delayed matches and gives operations teams one place to review the result.
Conversion operations
Matching overview
ReferenceSourceStatus
Order A-1049NorthstarMatched
Order A-1050HarbourMatched
Order A-1051MeadowWaiting
Order A-1052NorthstarMatched
Fictional sources and records
The requirement
Several sources needed to become one dependable workflow.
Each external source supplied conversion information in its own way and on its own schedule. The business needed a consistent process that could connect the records, keep delayed information in view and support everyday reporting.
- Bring click and conversion records into one consistent view
- Handle information arriving in different formats and at different times
- Keep unmatched records available for another attempt
- Give operations teams searchable reports and exports
- Send completed purchase events to site analytics consistently
The matching journey
A clear route from outbound click to completed record.
The application keeps the workflow understandable even when the two sides of the journey arrive hours or days apart.
- 01
Receive the click
A validated outbound click arrives from the WordPress collection tool and is stored against the correct site.
- 02
Receive the conversion
Conversion information later arrives from one of several external sources.
- 03
Find the connection
The application translates the incoming record and looks for the related click.
- 04
Report or retry
Matched records become available for reporting. Others remain in the delayed queue for another attempt.
What we built
One place to match, review and report.
The technical differences between sources are handled inside the application, leaving operations users with a consistent set of records and statuses.
One shared record
Different source formats are turned into a consistent click and conversion record for each site.
Delayed matching
A conversion that arrives too early or too late is held safely and checked again as more information becomes available.
Operational reporting
Users can search, filter and export click and conversion records from one protected workspace.
Consistent analytics
Completed conversion information can be sent back to the relevant site analytics in a standard form.
Delayed conversion queue
WaitingRecords stay in view
An unmatched conversion is not discarded. It remains available for scheduled checks until the related click can be found or the record needs review.
- ReferenceOrder A-1051
- SourceMeadow
- Next actionCheck again
- Reporting statusHeld safely
Fictional example
The outcome
Fragmented records became one operational process.
The platform gives the team a central place to handle different sources, delayed information, reporting and the analytics hand-off without pretending every conversion arrives neatly.
Joined-up records
Clicks and conversions brought together
Delayed matching
Later information kept available
Operational review
Searchable records and exports
Consistent analytics
Completed events prepared by site
Technology
The technology behind the work.
Laravel- PHP
- MySQL
- Livewire
- Background queues
- Google Analytics
About this project
- Sector
- Digital publishing
- Services
- Custom application development, data integration and reporting
- Project type
- Internal attribution platform
Need several data sources to work as one?
Tell us where the information comes from, when it arrives and what your team needs to do with it.