Understand the route your Google data takes
The WeProfit Google destination is GA4. Your GA4 property receives the events, and your linked Google Ads account can use the conversions you configure from that property. This setup is different from a direct Google Ads Enhanced Conversions integration.
Google describes Measurement Protocol as a supplement to browser collection. Keep the appropriate Google tagging in place and review identifiers and consent settings when you configure the connection.
Connect GA4 and configure Google Ads conversions
Start in WeProfit by connecting the GA4 destination using the property’s required connection details. Verify the event flow in GA4 before investigating whether Google Ads reports an attributed conversion.
- Connect the correct GA4 property to your store in WeProfit.
- Confirm the intended purchase events appear in that property.
- Link the GA4 property to the correct Google Ads account.
- Configure the relevant GA4 events as Google Ads conversions.
- Review conversion goals and primary or secondary settings to avoid duplicate bidding signals.
Check purchase definitions and overlapping goals
A store may already send purchases to GA4 or use a native Google Ads purchase conversion. Document those existing sources before adding another route.
Review transaction identifiers, event names, conversion counting, and which goals are used for bidding. Sending a purchase successfully does not by itself establish that the account should use it as an additional primary conversion.
Read GA4 and Google Ads in context
The same purchase may appear differently across store reporting, GA4, and Google Ads because the reports answer different attribution questions. Compare aligned date ranges and investigate individual events when there is a discrepancy.
WeProfit also supports Google Ads spend synchronization for its reporting. Spend import and conversion delivery are separate connections: enabling one does not automatically configure the other.