Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log more attribution params from AF #642

Open
pepf opened this issue Aug 15, 2022 · 0 comments
Open

Log more attribution params from AF #642

pepf opened this issue Aug 15, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@pepf
Copy link

pepf commented Aug 15, 2022

Summary

The current plugin cherry picks some fields from the Appsflyer payload to forward to Analytics.track():

const { af_status, media_source, campaign, is_first_launch } = res?.data;
const properties = {
provider: this.key,
campaign: {
source: media_source,
name: campaign,
},

The docs however indicate the payload can contain a lot more data, depending on various factors.
https://support.appsflyer.com/hc/en-us/articles/360000726098-Conversion-data-payloads-and-scenarios#deferred-deep-linking-with-srns

I understand this is where the Analytics.js "spec" for this event comes in, but would love to see a normalized way of retrieving some of the more granular data fields on the Appsflyer payload and forward them to Segment as event. A few fields I am specifically interested in:

  • ad_id
  • adset_id
  • adset

Proposed Solution

Looking at the docs I see the meaning of these fields varies per partner (google,facebook etc..) so if this is too scary to implement on your end, maybe exposing a "mapper function" so we can fill in the blank properties on our end would be great :)

@pepf pepf added the enhancement New feature or request label Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant