I looked into this today, and noticed we are currently not passing the contact_id/contact_hash from DonateWiki to PaymentsWiki.

This is to confirm that attribution for Fundraiseup transactions from 21st of November till date using the wmf_* fields have now been updated in Civi.

No worries @ppenloglou, yes I added those today for any other donation that comes in through the campaign.

Thanks @Pcoombe

Hi @RKumar_WMF, I can confirm the missing Fundraiseup transactions have been imported into Civi. However, for the other transactions, I'm unable to trace their origins as they are not Fundraiseup initiated transactions.

Some of this transactions are Fundraiseups, but not all. I checked our logs and noticed we weren't importing Fundraiseup transactions between 30th of July - 26th of August, so some Fundraiseup transactions weren't imported.

That's weird @Eileenmcnaughton, I looked around but couldn't find a reason to why the images would not render. I've created a section on our docs in Wikitech with these images and a description of what I had in mind.

This is currently blocked as the test transactions aren't completing.

This looks exciting, though not the complete 2 way sync we hoped for, but its reasonably close to it. From the documentation, some of the endpoints that would be useful include:

• Update donation and associated recurring plan endpoint (Link). This endpoint would allow recurring plan modifications to be done straight from Civi, making Civi the single source of truth. Through this endpoint, the donor record can also be modified from Civi and changes would reflect on Fundraiseup.

Hi @MSuijkerbuijk_WMF, I did some digging on this today and it seems the Conversion Tracking pixel can be setup through the Google Tag Manager as specified in Google docs.

I checked this once, I think it happens when the venmo/fundraiseup/gravy contribution isn't the contact's first contribution. We can fix this by updating the record with the new fields on contribution.

The Gravy-Trustly integration is blocked for the following reasons:

I'm working on this ticket but in order to understand the requirements/proposed solution, I've gone ahead to draw up a flow of how we currently manage contact emails and the proposed solution to prevent this overwrite.
Regular donations through Payment form (example CC)
{F57630733}

The Gravy-Braintree-Venmo integration is blocked for the following reasons:

The Gravy-Trustly integration is blocked for the following reasons:

Gravy sends messages for as the status changes for venmo transactions and refunds. The only message I wasn't able to test was for the Cancel transaction as I was unable to keep the transaction in an authorization state for cancellation. Gravy currently doesn't send messages for the partial refunds but we can get that in the audit.