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 StatusMeta EventGoogle (GA4) EventTikTok EventLinkedIn Event
pageviewPageViewpage_viewViewContentPAGE_VIEW
newAddToCartgenerate_leadViewContentPAGE_VIEW
contactedContactworking_leadContactCONTACT
respondedLeadworking_leadLeadLEAD
qualifiedLeadqualify_leadLeadQUALIFIED_LEAD
hotSubmitApplicationworking_leadSubmitApplicationQUALIFIED_LEAD
proposalInitiateCheckoutworking_leadInitiateCheckoutREQUEST_QUOTE
negotiationAddPaymentInfoworking_leadAddPaymentInfoREQUEST_QUOTE
invoiceAddPaymentInfoadd_payment_infoAddPaymentInfoREQUEST_QUOTE
wonPurchasepurchasePurchasePURCHASE
lostArchiveclose_unconvert_leadViewContentArchive
  • 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 (usually ViewContent or Contact).

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).

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.

  1. Open Google AdsGoalsConversions.
  2. Click the Conversion Action you want to use.
  3. On the details page, look at the URL in your browser.
  4. 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.

  1. Open Google AdsGoalsConversions.
  2. Click the Conversion Action you want to use.
  3. Go to Tag setup.
  4. Choose Tag Manager (or your preferred installation method).
  5. 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

You can change the standard event names above (e.g., change Purchase to Closing) via the Conversion Settings > Custom Event Mapping menu.

If you want to stop sending events for a specific status, select the dont_send option in the custom mapping dropdown. The system will skip processing for that event.

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:

EventDescriptionUse Case
Core Conversion
PurchasePurchase completedFinal checkout/payment
LeadSign up completedForm submissions
ContactContact initiatedWhatsApp, phone, chat
CompleteRegistrationRegistration completedAccount creation
Shopping Events
AddPaymentInfoPayment info addedPre-checkout step
AddToCartAdded to cartProduct interest
AddToWishlistAdded to wishlistProduct interest
InitiateCheckoutStarted checkoutCheckout intent
ViewContentViewed page/productProduct views
SearchPerformed searchSearch queries
Subscription Events
StartTrialStarted free trialTrial signups
SubscribeSubscribed to serviceSubscription conversions
Service Events
ScheduleBooked appointmentAppointment booking
FindLocationSearched for locationStore locator
SubmitApplicationSubmitted applicationApplications
CustomizeProductCustomized productProduct customization
DonateMade donationDonations

Konektor supports all GA4 Recommended Events. GA4 events use lowercase with underscores format:

EventDescriptionUse Case
Lead Lifecycle Events
generate_leadLead generatedForm submission, first contact
qualify_leadLead qualifiedLead scoring threshold
working_leadLead being workedFollow-up in progress
close_convert_leadLead successfully closedDeal won
close_unconvert_leadLead did not closeDeal lost
disqualify_leadLead disqualifiedNot qualified
E-commerce Shopping
purchasePurchase completedTransaction completed
add_to_cartAdded to cartProduct interest
add_to_wishlistAdded to wishlistProduct interest
remove_from_cartRemoved from cartCart abandonment
view_cartViewed cartCart review
view_itemViewed productProduct page view
view_item_listViewed product listCategory page
select_itemSelected productProduct selection
begin_checkoutStarted checkoutCheckout started
add_payment_infoPayment info addedPayment step
add_shipping_infoShipping info addedShipping step
searchPerformed searchSearch queries
refundRefund processedRefund processed
Promotion Events
view_promotionViewed promotionBanner views
select_promotionSelected promotionBanner clicks
Account Events
loginUser logged inLogin events
sign_upUser signed upRegistration
Engagement Events
shareContent sharedSocial sharing
select_contentContent selectedContent 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:

EventDescriptionUse Case
E-commerce Events
PurchasePayment completedTransaction completed
AddToCartAdded to cartProduct interest
AddToWishlistAdded to wishlistProduct interest
InitiateCheckoutCheckout startedCheckout started
AddPaymentInfoPayment info addedPayment step
ViewContentPage viewedPage/product view
SearchSearch performedSearch queries
Lead & Form Events
LeadForm submittedForm submissions
ContactContact occurredWhatsApp, phone, chat
CompleteRegistrationRegistration completedAccount creation
SubmitApplicationApplication submittedApplications
ApplicationApprovalApplication approvedApproval flows
Subscription Events
StartTrialTrial startedTrial signups
SubscribeSubscription madeSubscriptions
Service Events
ScheduleAppointment bookedAppointments
FindLocationLocation searchedStore locator
CustomizeProductProduct customizedProduct config
DownloadDownload clickedApp downloads
TikTok uses PascalCase format like Meta (e.g., 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:

EventDescriptionObjective
Conversion Events
PURCHASETransaction completedConversion
ADD_TO_CARTAdded to cartConversion
START_CHECKOUTStarted checkoutConversion
SIGN_UPAccount createdConversion
INSTALLApp installedConversion
Lead Events
LEADForm submittedLead Gen
CONTACTContact occurredLead
BOOK_APPOINTMENTScheduled meetingLead
REQUEST_DEMODemo requestedLead
DOWNLOADFile downloadedLead
Consideration Events
VIEW_CONTENTPage viewedConsideration
KEY_PAGE_VIEWKey page viewed (pricing)Consideration
SEARCHSearch performedConsideration
SUBSCRIBESubscribedConsideration
SAVESaved for laterConsideration
Other
OTHERCustom eventVaries

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_id when the event is sent. Click IDs such as gclid, wbraid, or gbraid still matter for attribution, but they do not replace ga_client_id in 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 skipped status 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.
Go to Settings > Conversion, then select an option in the Conversion Strategy section.

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

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.

Email Supportsupport@konektor.id
YouTubeYouTube

© 2026 Konektor. All rights reserved.