VITAL GUIDES

Narrow, technical guides for connecting Keap to the software your business actually runs on. Written from work we were paid to do, which is why they cover the parts the documentation leaves out. No gated PDFs, no email wall, no course.

KEAP, FROM THE API UP

What the API actually returns for deals, orders, write offs, custom fields and email engagement. Measured on live accounts, and dated so you know when.

01 KeapPipelinesREST v2Reporting Published

KEAP DEALS BY API: THE WRONG BASE PATH AND THE SORT THAT LOSES DEALS

Deals do not live where the docs point, the flat list answers 501, and the obvious sort order returned exactly the right row count with 1,133 deals missing. The base path, the sort key that does not lose rows, the one endpoint that tells you whether you got them all, and why a deal's value changes shape between read and write.

02 KeapOrdersAutomation Published

CREATE A PAID KEAP ORDER BY API, AND WHY YOUR AUTOMATION NEVER FIRED

An order created by API is a receivable, not a sale. The money is a second call, the field is not called what you think, and until it lands the customer's purchase automation never runs. The whole chain measured end to end, including the Product Purchase goal firing with no goal call at all.

03 KeapRevenueReporting Published

A KEAP WRITE OFF LOOKS EXACTLY LIKE A PAYMENT

A written off invoice reads PAID with the full amount in total_paid and is byte for byte identical to a real one. A naive revenue report counts the customer's own bad debt as sales, the refund field flips sign and unit between the two APIs, and the status never goes back once set. Measured across 1,487 live orders, with the settlement rule that gets the number right.

04 KeapCustom fields Published

KEAP CUSTOM FIELDS: THE CEILING, THE TAB YOU CANNOT MOVE, THE NAME YOU CANNOT GET BACK

The limit is not the documented 100, a contact field's tab can only be chosen at creation, and deleting a field burns its name for good, along with every hidden field and merge code that referred to it. How to make room on a mature app without destroying history, starting with measuring instead of sampling.

05 KeapEmailREST v2Reporting Published

GET EMAIL OPENS AND CLICKS OUT OF THE KEAP API

Everyone says the Keap API has no engagement data, so agencies fake it with tags. There is an endpoint. Last send, last open, last click and opt status for any address, measured across 25 live ones, plus the opt in repair that Keap's own compliance rule makes safe to offer.

06 KeapREST v2 Published

MIGRATE KEAP FROM XML-RPC TO REST v2 BEFORE THE SUNSET

Keap is turning off its oldest API, and plenty of businesses use it without knowing. What actually changes moving to REST v2, the OAuth switch, the endpoints with no equivalent yet, and the opt-in detail that quietly makes migrated contacts non-marketable while returning a clean 200.

ATTRIBUTION THAT SURVIVES

The plumbing between an ad click and a paid invoice, and the three places it quietly breaks: Safari, two writers on the books, and a campaign that never serves.

01 AttributionSafariTracking Published

WHY SAFARI KILLS YOUR ATTRIBUTION AFTER SEVEN DAYS, AND THE PROXY THAT FIXES IT

A visitor clicks your ad in week one and buys in week three, and on Safari the credit is gone. A first party cookie name is not enough: Safari capped ours at 7 days, and served through the site's own host the same cookie stored 400. What was measured, the proxy that fixes it, and the write once rule for first touch.

02 WooCommerceKeapQuickBooksRevenue Published

WOOCOMMERCE TO KEAP TO QUICKBOOKS: ONE SOURCE OF TRUTH, NOT TWO WRITERS

One plugin syncs the store to Keap, another syncs it to QuickBooks, and the two never agree because the books never met the customer record. A store sale reaches QuickBooks by becoming a CRM order first, with its payment recorded, which is also what fires the purchase automation. The topology and the three places it goes wrong.

03 Google AdsAttribution Published

YOUR GOOGLE SEARCH CAMPAIGN IS ELIGIBLE AND NEVER SERVES

Approved ad, approved billing, eligible keywords, zero impressions for a month. Eligible means allowed to run, not running. The three impression share numbers that say exactly why, the bid ceiling that was the cause on our own campaign, and the order to fix things in.

THE CLIENT LOOP, BOOKED TO BUILT

Booked, met, recapped, filed, the project built before anyone opens a laptop. Three guides, one tag at a time.

01 KeapClickUpAutomation Published

TURN A KEAP TAG INTO A BUILT CLICKUP PROJECT

One tag fires and the client's whole ClickUp structure exists: space, list, board, and a task carrying the discovery notes. Find or create at every step so a re-fired tag never duplicates anything, plus the auth gotcha that catches everyone exactly once.

02 CalendlyPower AutomateKeapAutomation Published

GET CALENDLY'S AI MEETING NOTES INTO KEAP

Note Taker writes the recap and emails it to you, where it dies. Parsing that email into real CRM fields, resolving them by label so adding one needs no redeploy, and why this guide matches on email when the last one told you never to.

03 CalendlyKeap Published

CONNECT CALENDLY TO KEAP WITHOUT ZAPIER

Every tutorial says match the booking to a contact by email. That advice is why your CRM has three records for the same person. The approach that never matches at all, works on the free Calendly plan, and costs nothing per booking.

Why these are so narrow. A guide called "CRM automation best practices" helps nobody. A guide called "connect Calendly to Keap without duplicate contacts" is the exact thing someone types at 11pm when their CRM has three of the same person in it. We write the second kind, because that is the kind we needed and could not find. Together they cover a client lifecycle that runs itself: booked, met, recapped, filed, the project built before anyone opens a laptop. Alongside that sits the deeper plumbing, like keeping your Keap integration alive through the XML-RPC sunset. The newer ones go where the documentation stops: what the Keap API actually returns for deals, orders, write offs, custom fields and email engagement, measured on live accounts and dated so you know when, and the attribution plumbing that has to survive Safari, two writers on the books, and a campaign that never serves. Same kind of guide throughout: the specifics, not the overview.

Rather not build it yourself?

WE HAVE BEEN DOING THIS
SINCE 2010.

Every guide here came out of work we were hired to do. If you would rather it just worked, that is a conversation we would enjoy having.

Book a Free Consult