Conversion Settings Configuration
The Conversion Settings page allows you to control how Konektor reports events/conversions back to ad platforms (Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads) when a Lead status changes.
This feature is very powerful for optimizing ads based on real results (Purchase/Closing) rather than just WA button clicks.
1. Event Mapping
Konektor uses Target Status logic to report conversions. The system no longer relies on "status changes" (e.g., A to B), but instead looks at the Final Status of the Lead.
This means as soon as a Lead reaches a specific status (whether upon initial entry or during an update), Konektor will send the corresponding event for that status to the ad platforms.
Default Mapping (Type: Sales)
The following is the standard mapping used by the system based on Lead Status:
| Lead Status | Meta Event | Google (GA4) Event | TikTok Event | LinkedIn Event |
|---|---|---|---|---|
pageview | PageView | page_view | ViewContent | PAGE_VIEW |
new | AddToCart | generate_lead | ViewContent | PAGE_VIEW |
contacted | Contact | working_lead | Contact | CONTACT |
responded | Lead | working_lead | Lead | LEAD |
qualified | Lead | qualify_lead | Lead | QUALIFIED_LEAD |
hot | SubmitApplication | working_lead | SubmitApplication | QUALIFIED_LEAD |
proposal | InitiateCheckout | working_lead | InitiateCheckout | REQUEST_QUOTE |
negotiation | AddPaymentInfo | working_lead | AddPaymentInfo | REQUEST_QUOTE |
invoice | AddPaymentInfo | add_payment_info | AddPaymentInfo | REQUEST_QUOTE |
won | Purchase | purchase | Purchase | PURCHASE |
lost | Archive | close_unconvert_lead | ViewContent | Archive |
pageview(Visitor): Used when the tracker (track.min.js) detects an initial visit. This status triggers the PageView event (if enabled/mapped).new(Lead): Used when a visitor takes a real action (like clicking a WhatsApp Rotator). This status will send the first conversion (usuallyViewContentorContact).
Note
Events are only sent once per event category (e.g., a Purchase event is only sent once even if the status is updated multiple times to won).
Google Ads: GA4 vs Ads API
Konektor supports two Google reporting paths:
- GA4: Events go to GA4 and you import them into Google Ads.
- Ads API: Events go directly to Google Ads through Direct Google Ads API (Advanced) using an Action ID.
If you use Ads API, the system uses the default Action ID from the Google Pixel first. In Conversion Settings, you only need to fill a per-status Action ID override when you want to replace the Action ID for a specific status. GA4 mapping still lives in the Google (GA4) column.
Conversion Label is only used for online tags (e.g., GTM). Ads API mode does not use Conversion Label.
Recommendation: use Ads API for bidding optimization and GA4 for additional analytics.
Official references:
How to find Action ID (Direct Google Ads API)
Use these steps when you use Ads API and need Action ID.
- Open Google Ads → Goals → Conversions.
- Click the Conversion Action you want to use.
- On the details page, look at the URL in your browser.
- Find the parameter ctId=123456789. The number after ctId is the Action ID.
The Action ID comes from ctId in the conversion action details URL. It is not the Conversion ID and not the Conversion Label shown in Tag setup.
How to find Conversion ID and Conversion Label (Google Ads)
Use these steps when you install online tags (GTM or gtag) and need Conversion ID and Conversion Label.
- Open Google Ads → Goals → Conversions.
- Click the Conversion Action you want to use.
- Go to Tag setup.
- Choose Tag Manager (or your preferred installation method).
- Copy the Conversion ID and Conversion Label shown there.
Official Google doc:
Example:
- Conversion ID:
1234567890 - Conversion Label:
AbCdEfGhIjKlMnOpQrSt
If you use Direct Google Ads API (Advanced), the system uses an Action ID. You can use one default Action ID in the Google Pixel, then add per-status overrides only when needed. Conversion Label is only required for online tags.
Custom Event Names
Loading...
Purchase to Closing) via the Conversion Settings > Custom Event Mapping menu.When the Action ID override field appears
The Google Ads (Action ID) field in Conversion Settings only appears when the Google Pixel is active in Ads API mode. If the Google Pixel is still using GA4 mode, the Action ID override field stays hidden.
2. Platform Standard Events
Meta Pixel Standard Events
When creating custom mappings, you can choose from all Meta Pixel Standard Events:
| Event | Description | Use Case |
|---|---|---|
| Core Conversion | ||
Purchase | Purchase completed | Final checkout/payment |
Lead | Sign up completed | Form submissions |
Contact | Contact initiated | WhatsApp, phone, chat |
CompleteRegistration | Registration completed | Account creation |
| Shopping Events | ||
AddPaymentInfo | Payment info added | Pre-checkout step |
AddToCart | Added to cart | Product interest |
AddToWishlist | Added to wishlist | Product interest |
InitiateCheckout | Started checkout | Checkout intent |
ViewContent | Viewed page/product | Product views |
Search | Performed search | Search queries |
| Subscription Events | ||
StartTrial | Started free trial | Trial signups |
Subscribe | Subscribed to service | Subscription conversions |
| Service Events | ||
Schedule | Booked appointment | Appointment booking |
FindLocation | Searched for location | Store locator |
SubmitApplication | Submitted application | Applications |
CustomizeProduct | Customized product | Product customization |
Donate | Made donation | Donations |
Google Analytics 4 (GA4) Recommended Events
Konektor supports all GA4 Recommended Events. GA4 events use lowercase with underscores format:
| Event | Description | Use Case |
|---|---|---|
| Lead Lifecycle Events | ||
generate_lead | Lead generated | Form submission, first contact |
qualify_lead | Lead qualified | Lead scoring threshold |
working_lead | Lead being worked | Follow-up in progress |
close_convert_lead | Lead successfully closed | Deal won |
close_unconvert_lead | Lead did not close | Deal lost |
disqualify_lead | Lead disqualified | Not qualified |
| E-commerce Shopping | ||
purchase | Purchase completed | Transaction completed |
add_to_cart | Added to cart | Product interest |
add_to_wishlist | Added to wishlist | Product interest |
remove_from_cart | Removed from cart | Cart abandonment |
view_cart | Viewed cart | Cart review |
view_item | Viewed product | Product page view |
view_item_list | Viewed product list | Category page |
select_item | Selected product | Product selection |
begin_checkout | Started checkout | Checkout started |
add_payment_info | Payment info added | Payment step |
add_shipping_info | Shipping info added | Shipping step |
search | Performed search | Search queries |
refund | Refund processed | Refund processed |
| Promotion Events | ||
view_promotion | Viewed promotion | Banner views |
select_promotion | Selected promotion | Banner clicks |
| Account Events | ||
login | User logged in | Login events |
sign_up | User signed up | Registration |
| Engagement Events | ||
share | Content shared | Social sharing |
select_content | Content selected | Content engagement |
GA4 Event Format
Note that GA4 uses lowercase with underscores format (e.g., generate_lead, add_to_cart), unlike Meta which uses PascalCase (e.g., Lead, AddToCart).
TikTok Events API Standard Events
Konektor supports all TikTok Events API Standard Events. TikTok Events use PascalCase format:
| Event | Description | Use Case |
|---|---|---|
| E-commerce Events | ||
Purchase | Payment completed | Transaction completed |
AddToCart | Added to cart | Product interest |
AddToWishlist | Added to wishlist | Product interest |
InitiateCheckout | Checkout started | Checkout started |
AddPaymentInfo | Payment info added | Payment step |
ViewContent | Page viewed | Page/product view |
Search | Search performed | Search queries |
| Lead & Form Events | ||
Lead | Form submitted | Form submissions |
Contact | Contact occurred | WhatsApp, phone, chat |
CompleteRegistration | Registration completed | Account creation |
SubmitApplication | Application submitted | Applications |
ApplicationApproval | Application approved | Approval flows |
| Subscription Events | ||
StartTrial | Trial started | Trial signups |
Subscribe | Subscription made | Subscriptions |
| Service Events | ||
Schedule | Appointment booked | Appointments |
FindLocation | Location searched | Store locator |
CustomizeProduct | Product customized | Product config |
Download | Download clicked | App downloads |
Purchase, AddToCart). Make sure to use the exact event names as they are case-sensitive.LinkedIn Conversions API Events
Konektor supports all LinkedIn Conversion Categories. LinkedIn uses UPPERCASE format:
| Event | Description | Objective |
|---|---|---|
| Conversion Events | ||
PURCHASE | Transaction completed | Conversion |
ADD_TO_CART | Added to cart | Conversion |
START_CHECKOUT | Started checkout | Conversion |
SIGN_UP | Account created | Conversion |
INSTALL | App installed | Conversion |
| Lead Events | ||
LEAD | Form submitted | Lead Gen |
CONTACT | Contact occurred | Lead |
BOOK_APPOINTMENT | Scheduled meeting | Lead |
REQUEST_DEMO | Demo requested | Lead |
DOWNLOAD | File downloaded | Lead |
| Consideration Events | ||
VIEW_CONTENT | Page viewed | Consideration |
KEY_PAGE_VIEW | Key page viewed (pricing) | Consideration |
SEARCH | Search performed | Consideration |
SUBSCRIBE | Subscribed | Consideration |
SAVE | Saved for later | Consideration |
| Other | ||
OTHER | Custom event | Varies |
LinkedIn Conversion ID
Each conversion category in LinkedIn requires a unique Conversion ID created in Campaign Manager. One ID cannot be used for two different purposes.
3. Conversion Strategy (Strict vs Send All)
Konektor provides flexibility in how you send conversion data. You can choose this strategy in the Settings > Conversion menu.
Option 1: Strict Mode (Default)
To maintain your ad algorithm data quality and prevent organic data from mixing with ad data.
Note
Read the full comparison between strategies in the Conversion Strategy Guide.
- How it Works: Conversion events are only sent when the minimum platform-specific data is available.
- Google GA4: Requires
ga_client_idwhen the event is sent. Click IDs such asgclid,wbraid, orgbraidstill matter for attribution, but they do not replacega_client_idin this mode. - Google Ads API: Can use
gclid,wbraid,gbraid, or sufficient hashed identifiers for direct upload. - "Skipped" Status: If the minimum data is missing, the system records a
skippedstatus in the sync logs. - Benefits: 100% attribution accuracy (Clean ROI). Ad platforms only receive data from actual ad clicks.
Option 2: Send All Events
To maximize data signals for the ad algorithm (AI Learning).
- How it Works: Sends all qualifying conversion events, regardless of whether a Click ID exists.
- Matching: Platforms will use hashed personal data (Email/Phone) to match users (Advanced Matching).
- Benefits: Helps ad algorithms learn faster and capture Cross-Device conversions.
Detailed statuses in Sync Logs
No matter which strategy you use, Sync Logs still uses the same detailed statuses:
accepted: the platform accepted the payload.partial_failure: the request was accepted, but some data was rejected or returned warnings.failed: the request failed before the platform accepted it.skipped: the event was intentionally not sent because the minimum data, consent, or configuration was not sufficient.
4. Value Settings
Loading...
Konektor allows you to send monetary value (revenue) to ad platforms to calculate ROAS (Return on Ad Spend) accurately.
- Estimated Value: The estimated value when the lead first enters.
- Actual Value: The real transaction value (e.g., the final deal value).
- Fixed Value: A fixed value for every conversion (e.g., IDR 10,000 per lead).
Value Input Popup (Modal Trigger)
You can enable an automatic popup that asks the CS to input the deal value when changing a lead status to a specific status (e.g., won or invoice). Enable trigger statuses via the Modal Trigger Statuses field.
5. Supported Platforms
Konektor supports modern server-side integrations for:
- Meta Ads: Via Conversions API (CAPI).
- Google Ads: Via Enhanced Conversions.
- TikTok Ads: Via Events API.
- LinkedIn Ads: Via Conversions API.
Ensure you have completed the necessary configuration in the Pixels menu.
Need More Help?
Our team is ready to help you maximize ad tracking and business attribution.
© 2026 Konektor. All rights reserved.
