How to connect Loyverse and Google Ads
Create a New Scenario to Connect Loyverse and Google Ads
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Loyverse, triggered by another scenario, or executed manually (for testing purposes). In most cases, Loyverse or Google Ads will be your first step. To do this, click "Choose an app," find Loyverse or Google Ads, and select the appropriate trigger to start the scenario.

Add the Loyverse Node
Select the Loyverse node from the app selection panel on the right.


Loyverse

Configure the Loyverse
Click on the Loyverse node to configure it. You can modify the Loyverse URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Google Ads Node
Next, click the plus (+) icon on the Loyverse node, select Google Ads from the list of available apps, and choose the action you need from the list of nodes within Google Ads.


Loyverse
⚙
Google Ads

Authenticate Google Ads
Now, click the Google Ads node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Google Ads settings. Authentication allows you to use Google Ads through Latenode.
Configure the Loyverse and Google Ads Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Loyverse and Google Ads Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Google Ads
Trigger on Webhook
⚙

Loyverse
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Loyverse, Google Ads, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Loyverse and Google Ads integration works as expected. Depending on your setup, data should flow between Loyverse and Google Ads (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Loyverse and Google Ads
Loyverse + Mailchimp + Google Ads: When a new customer is added in Loyverse, they are added to a Mailchimp list and then added to a Google Ads customer list for targeted advertising campaigns.
Google Ads + Loyverse + Google Sheets: This workflow tracks ad spend by retrieving campaign data from Google Ads and combines it with sales data from Loyverse, then reports ROI in Google Sheets for informed decision-making.
Loyverse and Google Ads integration alternatives

About Loyverse
Sync Loyverse sales data to your accounting or marketing tools using Latenode. Automate inventory updates based on Loyverse transactions. Trigger custom workflows for customer loyalty programs. Latenode lets you connect Loyverse data to any app without code, adding powerful automation to your POS system.
Related categories
About Google Ads
Use Google Ads in Latenode to automate campaign management and reporting. Pull ad performance data, adjust bids based on real-time events, or trigger alerts for budget changes. Combine with other apps to build custom marketing workflows. Latenode's flexibility avoids rigid, pre-built integrations and costly per-step pricing.
Similar apps
Related categories
See how Latenode works
FAQ Loyverse and Google Ads
How can I connect my Loyverse account to Google Ads using Latenode?
To connect your Loyverse account to Google Ads on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Loyverse and click on "Connect".
- Authenticate your Loyverse and Google Ads accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track offline Loyverse sales in Google Ads?
Yes, you can! With Latenode, easily send Loyverse sales data to Google Ads for enhanced conversion tracking. Optimize campaigns based on actual offline revenue and improve ROI using no-code.
What types of tasks can I perform by integrating Loyverse with Google Ads?
Integrating Loyverse with Google Ads allows you to perform various tasks, including:
- Automatically creating Google Ads remarketing lists from Loyverse customer data.
- Triggering Google Ads campaign adjustments based on Loyverse sales performance.
- Sending Loyverse loyalty program data to Google Ads for personalized ad campaigns.
- Updating Google Ads audiences with new Loyverse customer sign-ups in real-time.
- Reporting Loyverse sales conversions directly within Google Ads dashboards.
How do I handle currency conversions when sending data from Loyverse?
Latenode provides built-in currency conversion tools. Use JavaScript steps or AI blocks to automatically convert currencies.
Are there any limitations to the Loyverse and Google Ads integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical Loyverse data might require batch processing due to API limits.
- Complex Google Ads campaign structures may need custom JavaScript for full support.
- Real-time data synchronization is subject to Loyverse and Google Ads API availability.