-
Notifications
You must be signed in to change notification settings - Fork 113
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
fix: enhancement and version upgrade of google adwords enhanced conversion #2947
Conversation
Important Auto Review SkippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChat with CodeRabbit Bot (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2947 +/- ##
========================================
Coverage 87.19% 87.19%
========================================
Files 860 860
Lines 29326 29327 +1
Branches 6845 6845
========================================
+ Hits 25570 25571 +1
Misses 3410 3410
Partials 346 346 ☔ View full report in Codecov by Sentry. |
@@ -77,6 +77,8 @@ const processTrackEvent = async (metadata, message, destination) => { | |||
const payload = constructPayload(message, updatedMapping); | |||
|
|||
payload.partialFailure = true; | |||
// ref: https://developers.google.com/google-ads/api/docs/release-notes#:~:text=Added%20job_id%20as,UploadConversionAdjustmentsRequest | |||
payload.jobId = metadata.jobId; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we support properties.jobId as well? Some customer might try to provide jobId from their own.
CC @shrouti1507 @krishna2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you tell what's the use-case of customer for providing jobId when destination has ability to generate jobId in case of null ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Customer can maintain some unique numbers on their database and send that as jobId.
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
@@ -77,6 +77,8 @@ const processTrackEvent = async (metadata, message, destination) => { | |||
const payload = constructPayload(message, updatedMapping); | |||
|
|||
payload.partialFailure = true; | |||
// ref: https://developers.google.com/google-ads/api/docs/release-notes#:~:text=Added%20job_id%20as,UploadConversionAdjustmentsRequest | |||
payload.jobId = metadata.jobId; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shrouti1507 There's no point of introducing jobId
in this PR without handling partial failure feature
Restrict the PR only to version upgrade changes & create separate task for |
for now we are just adding support for v15 at #2966 |
What are the changes introduced in this PR?
resolves INT-976
This PR is divided into destination level changes
Google has got a new API version 15. We are updating API version of
Google adwords enhanced conversion
Also we are adding support of the new fields added by google for this above destination
Doc references :
enhanced conversion --> adding job_id https://developers.google.com/google-ads/api/rest/reference/rest/v15/customers/uploadConversionAdjustments#ConversionAdjustment
Please explain the objectives of your changes below
Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here
Type of change
enhancement
Existing capabilities/behavior
Same
New capabilities/behavior
added job Id value for conversions object.
If the pull request is a new feature,
Any technical or performance related pointers to consider with the change?
N/A
Any new dependencies introduced with this change?
N/A
Any new generic utility introduced or modified. Please explain the changes.
N/A
If the PR has changes in more than 10 files, please mention why the changes were not split into multiple PRs.
N/A
If multiple linear tasks are associated with the PR changes, please elaborate on the reason:
N/A
Developer checklist
No breaking changes are being introduced.
Are all related docs linked with the PR?
Are all changes manually tested?
Does this change require any documentation changes?
Are relevant unit and component test-cases added?
Reviewer checklist
Is the type of change in the PR title appropriate as per the changes?
Verified that there are no credentials or confidential data exposed with the changes.