---
title: Code Install Submission
description: Step-by-step instructions for submitting SEM Tracking Code Install requests from a Company record in HubSpot.
---

[Skip to content](https://hubspot.logicalposition.com/migration/knowledge/code-install-submission#main-content)

English

Show submenu for translations

![LPLogo\_White\_Horizontal.png\]](https://hubspot.logicalposition.com/hs-fs/hubfs/LPLogo_White_Horizontal.png?height=40&name=LPLogo_White_Horizontal.png)

- [Default HubSpot Blog](http://blog.logicalposition.com/)

Open main navigation

Close main navigation

- [Default HubSpot Blog](http://blog.logicalposition.com/)
- English
  
  Show submenu for translations
- Go to logicalposition.com

 Go to logicalposition.com

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Help Center](https://hubspot.logicalposition.com/migration/knowledge?hsLang=en)
2. [Support Teams](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en)
3. [Code Install](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en#code-install)

# Code Install Submission

## Step-by-step instructions for submitting SEM Tracking Code Install requests from a Company record in HubSpot.

### Overview

All Integration Requests (Data Feed New Builds, Data Feed Change Requests, SEM Tracking Code Installs, and SEM Tracking Troubleshooting)are submitted through the **Feed & Web Integration Requests** pipeline. This replaces the previous Quickbase process.

One key change from Quickbase: Integration requests are now submitted at the **Company level**, not the Service level. This change enables users to submit one request for multiple Services, rather than submitting multiple requests. You can tag multiple services on a single request during the request creation process.

---

### **Always submit from the Company record.** Submitting from anywhere else will prevent the assignee from auto-populating correctly.

---

### Submission Steps

1. **Open the Company record** for the client.
2. **In the Tickets card** (right column), click **+Add** to open the Create Ticket form.
3. **Enter a Ticket Name.** Any brief title works — it will be renamed automatically after creation.
4. **Select Pipeline:** Feed & Web Integration Requests.
5. **Select Integrations Request Type:** 
     1. SEM Tracking – Code Install
     2. SEM Tracking - Troubleshooting
6. **Complete the Dependent Properties.** Fill out every field you can. Asterisked (\*) fields are required. Use the **Back Office Ticket Attachments** field to attach PDFs, screenshots, or other supporting files.
7. **Associate the relevant Service(s).** Scroll to the bottom of the form and tag every Service this request applies to. If it covers multiple services, tag all of them.
8. **Click Create.**

### What Happens Automatically

Once the ticket is created, HubSpot will:

- **Rename the ticket** to: *\[Ticket Name\] - SEM Tracking – Code Install – \[Company Name\]*
- **Set the status** to New Request
- **Assign the ticket** to the SEM Tracking Specialist listed on the Company record
- **Set you as Ticket Owner** (update this if you're submitting on behalf of someone else)
- **Calculate the Requested Date of Completion** based on the Priority you selected:

| Priority | Turnaround |
| --- | --- |
| Low | 7 Business Days |
| Medium | 5 Business Days |
| High | 2 Business Days |
| Urgent | 24 Business Hours |

- **Send you a confirmation email** with the assignee and estimated completion date
- **Create a "Verify Website Credentials" task** for the SEM Tracking Specialist

### After Submission

Submission is done. The ticket moves to the SEM Tracking Specialist to manage. Watch for:

- **@mentions in notes or comments** — respond directly in HubSpot
- **A "Blocked" status email** — this means the Specialist needs something from you to keep moving

### Need Help?

Ask the **HubSpot Assistant (Integration Request bot)** — it's loaded with supporting documentation. If it can't answer your question, reach out to **Tristan Storr** directly.

---

Let me know if you'd like it tightened further, reframed for a specific audience (e.g., just AMs vs. Specialists), or if you want a matching article for the Troubleshooting request type.

- [Account Managers](https://hubspot.logicalposition.com/migration/knowledge/account-managers?hsLang=en#main-content)

    - [Submitting Quickbase Requests from HubSpot](https://hubspot.logicalposition.com/migration/knowledge/account-managers?hsLang=en#submitting-quickbase-requests-from-hubspot)
    - [HubSpot Co-Pilot](https://hubspot.logicalposition.com/migration/knowledge/account-managers?hsLang=en#hubspot-co-pilot)
    - [Quick Guides](https://hubspot.logicalposition.com/migration/knowledge/account-managers?hsLang=en#quick-guides)
    - [On-Boarding](https://hubspot.logicalposition.com/migration/knowledge/account-managers?hsLang=en#on-boarding)
- [Product Specialists](https://hubspot.logicalposition.com/migration/knowledge/product-specialists?hsLang=en#main-content)

    - [Project Management](https://hubspot.logicalposition.com/migration/knowledge/product-specialists?hsLang=en#project-management)
    - [Dashboard & Navigation](https://hubspot.logicalposition.com/migration/knowledge/product-specialists?hsLang=en#dashboard-navigation)
- [Support Teams](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en#main-content)

    - [Data Feed](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en#data-feed)
    - [Code Install](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en#code-install)
    - [Creative Services](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en#creative-services)

- [Default HubSpot Blog](http://blog.logicalposition.com/)

[![](https://hubspot.logicalposition.com/hubfs/logo-lp-agency-andromeda.svg)](https://lp.agency/)

logicalposition.com Help Center

Copyright © 2026, Logical Position