[MBL-873] Setup TriggerThirdPartyEvent GraphQL Mutation #1833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📲 What
We need to update our GraphSchema so that we can use the new
TriggerThirdPartyEvent
mutation.🤔 Why
This mutation allows us to send both facebook ad and google analytics data relevant to the user.
The backend will now determine which third party to use for us. For more details please see the engineering plan that I wrote for this.
🛠 How
Service
andServiceType
TriggerThirdPartyInput
TriggerThirdPartyEvent.graphql
in /mutationsThe work to address replacing existing triggerCapiEventInput calls will be done in the next PR.
That will also clean up all TriggerCapiEventInput related files.
✅ Acceptance criteria
TriggerThirdPartyEvent
mutation is ready to be referenced in the app.