# How do SmartMoving integrations connect marketing to booked moves? SmartMoving receives website forms and third-party leads through its Lead API, with referral sources, campaign fields, and branch routing. Its separate Open API lets Growth Plan users read business data, and the Premium API tier adds webhooks. Reporting booked moves to Google Ads, Google Analytics, or a call tracking tool requires a further connection that matches each booking to the original inquiry. - Canonical URL: https://movermarketing.ai/integrations/smartmoving - Integrations: https://movermarketing.ai/integrations - Publisher: Mover Marketing AI ## How leads reach SmartMoving ### How can our website form send leads to SmartMoving? The Lead API can turn submissions from an existing form into new SmartMoving leads. The documented fields include contact details, move date, origin, destination, notes, and service type, including Commercial. Map the details your sales team needs for an office walkthrough or an interstate estimate to those fields. SmartMoving also offers an embedded form and a WordPress plugin, but neither supports its UTM campaign fields. Choose an advanced form connection when you need campaign reporting. The Lead API is separate from the Open API and is available on all SmartMoving plans. ### How do purchased leads reach the right branch? Enable a supported provider under Sales > Lead Providers and share the vendor's connection instructions through an approved channel. SmartMoving lets you generate a provider connection for a specific branch; otherwise, leads go to your account's primary branch. Agree on routing before a provider starts sending interstate inquiries or office relocation requests. For a provider outside the supported list, SmartMoving documents a Custom Lead Provider option. Set its referral label deliberately: the custom-provider guide says leads otherwise carry the source Custom Lead Provider, which makes several providers harder to distinguish in reports. ### How do phone inquiries become CRM leads? For an inbound call, your team needs a lead-entry process or a custom connection that sends the caller's collected details through the documented Lead API. The RingCentral integration supports outbound calling from SmartMoving; its FAQ says you cannot answer calls in SmartMoving. A phone connection therefore needs its own intake plan. Record the inquiry's source when the lead is created, and decide how your team will match later calls to that record. Before connecting a call tracking tool, confirm its own supported data and connection options rather than assuming SmartMoving includes a ready-made connector. ### How does MMAI send website inquiries to SmartMoving? MMAI submits website leads to SmartMoving through its lead provider interface. The delivery plan should include a separate email copy, as SmartMoving recommends, so your team can see an inquiry during a connection failure. SmartMoving rejects duplicate submissions with a specific error; the form should tell the customer that the inquiry has already arrived. An unclear delivery result needs review before another submission. For help with your website form and source mapping, ask MMAI to review the connection your moving company uses. ## How results get back to your ads ### Which source fields should stay with each lead? Keep the referral source and campaign details separate. SmartMoving recommends that the ReferralSource field exactly match a configured source description; a new value creates another source record. Omitting the field in the website Lead API makes the source Your Website. Use agreed labels instead of unrestricted text. SmartMoving also supports seven UTM fields, including source, medium, campaign, ad group, and keyword. Its Lead Source and Conversion Analysis report can show those fields across leads with a booked date. Use the report to review where booked work came from, while checking that each form actually sends the campaign fields. ### How can booked moves get back to Google Ads? For booked-move reporting, plan a custom connection that reads SmartMoving data through the Open API or uses Premium webhooks for relevant changes. Define the booking milestone, then match it to the original inquiry. For Google's click-ID import route, capture the GCLID from the ad visit and store it with the prospect; send that identifier back with the conversion type and time. Campaign names alone cannot complete that match. Google recommends enhanced conversions for leads for new setups and directs new programmatic uploads to the Data Manager API. Confirm consent, account access, the import method, and its conversion window before treating a booked move as a reported ad conversion. ### How can Google Analytics receive the booking outcome? Google Analytics can receive offline events through its Measurement Protocol, alongside website tagging. For a custom booking connection, plan to send a confirmed booking as an event with the Analytics client identifier collected on the website. Keep that identifier in a record that links the lead to the booking. Google recommends the Data Manager API for new server-to-server event integrations, while Measurement Protocol remains operational. Keep customer names, email addresses, phone numbers, and raw CRM notes out of Analytics events and campaign fields. Google's Analytics policy prohibits sending personally identifiable information. ### How can call tracking reports show which calls became jobs? Plan an explicit match between the call tracking record and the SmartMoving inquiry, then send the verified booking outcome through a method the call tracking vendor supports. Confirm that vendor's ability to receive outcomes before choosing the connection. SmartMoving's Open API supplies a documented route for custom reporting, and Premium includes webhooks for events related to leads and jobs. These features do not establish a native booked-job connection to every call tracking tool. Agree on the record match and booking definition so a repeat call, an existing customer, or an unbooked estimate does not become another reported job. ## What SmartMoving does not do - The Lead API creates incoming leads. It does not by itself send booked-job conversions to Google Ads, Google Analytics, or call tracking tools. - SmartMoving documents Open API access for Growth Plan users. Basic access is read-only and excludes webhooks; Premium adds write access and webhooks. Confirm your account's access before planning outcome reporting. - Custom Lead API fields go into lead notes. Confirm how your connection will store and retrieve the Google click identifier before planning conversion uploads; do not assume lead notes provide a dedicated reporting field. - The embedded form and SmartMoving WordPress plugin do not support UTM fields. RingCentral's SmartMoving integration supports outbound calls only. Neither replaces an inbound-call attribution plan. ## FAQs ### Do we need SmartMoving's Open API to connect a website form? No. SmartMoving documents a separate Lead API for custom website forms and third-party lead sources, available on all plans. The Open API serves broader data access and custom reporting needs. ### Will SmartMoving automatically know which Google campaign produced a lead? Your form connection must send the supported campaign fields. The embedded form and SmartMoving WordPress plugin do not support UTMs. Referral labels also need explicit mapping; the website Lead API defaults to Your Website when you omit ReferralSource. ### Does receiving a lead complete Google Ads offline conversion tracking? No. The connection must match the later booking to the original ad interaction and upload the conversion through a supported Google method. SmartMoving lead delivery and Google conversion reporting are separate parts of the setup. ### Can the same connection handle commercial and long-distance inquiries? The Lead API supports a Commercial service type and origin and destination fields. Use those documented fields to send the information you collect for each inquiry, then agree on branch routing and the sales milestone you will report as booked. ## Sources - [SmartMoving Lead API integration guide](https://help.smartmoving.com/en/articles/3994387-smartmoving-lead-api-integration-guide) - [SmartMoving website connection options](https://help.smartmoving.com/en/articles/3269925-how-to-connect-your-website-to-smartmoving-lead-form-plugins-and-api-options) - [SmartMoving lead provider configuration](https://help.smartmoving.com/en/articles/3178641-enabling-and-configuring-lead-providers) - [SmartMoving custom lead providers](https://help.smartmoving.com/en/articles/8376727-custom-lead-provider) - [SmartMoving UTM tracking and booked-date reporting](https://help.smartmoving.com/en/articles/8945516-tracking-utms-in-smartmoving) - [SmartMoving Open API and webhooks](https://help.smartmoving.com/en/articles/9739804-smartmoving-s-open-api) - [SmartMoving RingCentral limitations](https://help.smartmoving.com/en/articles/7826768-ringcentral-faqs) - [Google Ads offline conversion imports](https://support.google.com/google-ads/answer/2998031?hl=en) - [Google Ads GCLID capture requirements](https://support.google.com/google-ads/answer/7012522?hl=en) - [Google Analytics offline event collection](https://developers.google.com/analytics/devguides/collection/protocol/ga4) - [Google Analytics personal data restrictions](https://support.google.com/analytics/answer/6366371?hl=en) SmartMoving is a trademark of its owner. Mover Marketing AI is not affiliated with or endorsed by SmartMoving.