Add Billing With Purchase analytics tags#1529
Conversation
|
Could I get some context on why this is being added? Why is it needed? |
For the Billing With Purchase feature we need to tell analytics when the merchant requested a billing agreement (shouldRequestBillingAgreement == true) so our observability dashboards can separate those flows from regular checkout. Right now there isn’t a tag on analytics events that indicates whether the request was Billing With Purchase, so we can’t see that clearly on the merchant or PayPal app side. Adding billing_with_purchase to the analytics payload fixes that. |
PayPal/src/main/java/com/braintreepayments/api/paypal/PayPalPaymentAuthRequestParams.kt
Outdated
Show resolved
Hide resolved
|
Looks like the one instrumentation test that is failing is the local payments test relating to the issue we are tracking. We'll go ahead a merge this when that issue is resolved |
jaxdesmarais
left a comment
There was a problem hiding this comment.
I left some comments on the iOS PR - lets align on naming across both platforms
|
@jaxdesmarais I responded to your comments and updated PR description with latest evidence. Are we still waiting on failing instrumentation tests to be fixed? |
| private const val FPTI_KEY_FUNDING_SOURCE = "funding_source" | ||
|
|
||
| private const val FPTI_KEY_IS_BILLING_AGREEMENT = "is_billing_agreement" | ||
| private const val FPTI_KEY_BILLING_PLAN_TYPE = "billing_plan_type" |
There was a problem hiding this comment.
Small nit to add a space between FPTI_KEYs and FPTI_BATCH_KEYs
Summary of changes
is_billing_agreement, andbilling_plan_typeto AnalyticsParamRepository so that it is sent with analytic events.isBillingAgreementtoisVaultRequestinPayPalPaymentAuthRequestParamsto be repurposed for these changes.Checklist
Screenshots
075999814R484453G - had
shouldRequestBillingAgreementas false, and did not setrecurringBillingPlanType.93A012420S1215734 - had
shouldRequestBillingAgreementas true, and setrecurringBillingPlanTypetoRECURRINGAuthors