Abstract

In some mobile app conversion tracking scenarios, attribution parameters on post-install engagement (PIE) events may be inconsistently transmitted, leading to potential gaps in measurement. A method is described to address this using a server-side stitching mechanism that can utilize a vendor identifier (e.g., an identifier for vendors or an application set identifier). During an initial app landing event where attribution parameters are present, a subset of data from these parameters may be stored on a server and keyed using the vendor identifier. For subsequent PIE events from the same app that lack these parameters, the system can use the vendor identifier to look up and stitch the previously stored attribution data to the current event. This process can improve conversion attribution coverage by re-establishing a link between later user engagements and the original ad interaction, potentially mitigating measurement loss and contributing to more complete and accurate reporting.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS