--- title: Managing Data Feed Requests description: A step-by-step guide to working a Data Feed ticket from intake through closure in HubSpot. --- [Skip to content](https://hubspot.logicalposition.com/migration/knowledge/managing-data-feed-requests#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. [Data Feed](https://hubspot.logicalposition.com/migration/knowledge/support-teams?hsLang=en#data-feed) # Managing Data Feed Requests ## A step-by-step guide to working a Data Feed ticket from submission through closure in HubSpot. ### Overview When a Data Feed request is submitted, it lands in your queue already set up with an assignee, priority-driven deadlines and a follow-up date,. Your job is to move the ticket through its lifecycle, auditing, working, notating, and closing, while keeping the ticket itself as the single source of truth. This guide walks through that lifecycle step-by-step. --- ### 1. What You Receive at Intake When a Data Feed ticket is submitted, HubSpot automatically: - Places the ticket in **New Request** status - Assigns it to you based on the Data Feed Specialist value on the Company record - Sets the **Requested Date of Completion** based on priority - Sets a **Ticket Follow-Up Date** as a prompt for first touch - Creates an auto-generated note summarizing the request details - Creates an **Audit Change Request** task for you #### Turnaround times by priority | Priority | Requested Completion | Follow-Up Date | | --- | --- | --- | | Low | 7 business days | 2 days out | | Medium | 5 business days | 2 days out | | High | 2 business days | 1 day out | | Urgent | 24 business hours | 1 day out | --- ### 2. Audit the Request Before starting work, review the ticket to confirm you understand the ask. **Where to look:** - **Left column — Integrations Request Information card:** request type, follow-up date, requested completion date - **Left column — Data Feed Information card:** Change Request Type, Ad Platform, Program, Existing Accounts, Launch Date - **Central column — Company Data Feed Information card:** standing client data sourced from the Company record - **Right sidebar:** confirm the associated Company and Service records look correct - **Activity feed:** read the auto-generated note summarizing the submission **What to do:** 1. Read the submission and auto-generated note in full. 2. Confirm you understand the scope, services affected, and any dependencies. 3. In the **Integrations Ticket Tracker** card, move the status from **New Request** → **Audited**. **What Audited means:** The request has been reviewed and understood, but active work has not started yet. --- ### 3. Start Work — Move to In-Progress When you actually begin the work, move the ticket from **Audited** → **In-Progress** using the Integrations Ticket Tracker. While in In-Progress: - Keep the **Ticket Follow-Up Date** current - Push this date out as circumstances change so nothing slips. - Document what you do using **Notes** (see Section 4). - Use **Tasks** to organize specific next actions for yourself (see Section 4). --- ### 4. Notes vs. Tasks — Use Them Correctly This is the most important habit to build. Notes and Tasks do different jobs. | | Notes | Tasks | | --- | --- | --- | | **Purpose** | **Output** — what was done | **Input** — what needs to be done | | **When to create** | After completing a meaningful piece of work | When you need to track a discrete work item for yourself | | **Best practice** | Be specific about what happened and why | Give it a title, due date, and (optionally) a description | Together, Notes and Tasks appear chronologically in the ticket's activity feed and create the paper trail for the request. #### **Tagging people** Use **@mentions** in notes to loop in the account manager, submitter, or anyone else who needs visibility. Tagged users receive a HubSpot notification. #### **Using comments** Both Notes and Tasks have a comment section. Use comments for back-and-forth on a specific item — e.g., the AM responding to a question you flagged. Everything stays logged on the ticket. #### **Snippets for completion notes** Type `#` in a note body to access pre-built templates (Snippets) for standardized completion notes. Shorthand codes are shared by the team separately. - *#crdone - Data Feed Change Request Completion Template* - *#nbdone - Data Feed New Build Completion Template* - *#promo - Data Feed Promotion Template* --- ### 5. When You're Stuck — Use Blocked Move a ticket to **Blocked** as soon as anything prevents progress. Common reasons include missing client info, a dependency on another team, platform or access issues. When this happens, the Ticket Owner receives an automated email that the ticket is blocked. #### **Recommended protocol** 1. Move the ticket to **Blocked**. 2. Create a **Note** explaining: - What the blocking issue is - Why work can't continue - What's needed to resolve it 3. **@mention** the account manager or ticket submitter in the note. 4. Use the note or task **comment section** for the back-and-forth conversation so it's documented in HubSpot. 5. Optionally send a Teams message or email as backup for visibility. #### **Once the block is resolved** 1. Move the ticket back to **In-Progress** (or whichever status is appropriate next). --- ### 6. When Work Is Done but Awaiting Confirmation (Pending Review & Approval) Use **Pending Review & Approval** when your work is complete but you're waiting on external confirmation before closing (e.g., Google Merchant Center product approval, Microsoft Advertising Store approval, or client confirmation that tracking is working.) - Use the **Follow-Up Date** field to track when you expect to check again. #### Once approval is confirmed 1. Proceed to close the ticket (Section 7). --- ### 7. Closing the Ticket Before moving to **Closed Request**: 1. Create a **final completion note** summarizing: - What work was done - Why it was done - Any follow-up items or important context 2. Move the ticket status to **Closed Request**. > **Important:** Once a ticket is Closed Request, no further automations will fire and no additional work should be recorded on it. If more work is needed, submit a new ticket. --- ### Full Workflow at a Glance 1. Ticket arrives in **New Request**. 2. Review request details, associations, Company Data Feed info, and the auto-generated note. 3. Move to **Audited** once you understand the request. 4. Move to **In-Progress** when active work starts. 5. Keep the **Follow-Up Date** current throughout. 6. Use **Tasks** for work to do; use **Notes** for work completed. 7. If blocked, move to **Blocked**, leave a note, tag the right people, and work from the note/task comments until resolved. 8. If waiting on outside confirmation, move to **Pending Review & Approval** and manage the follow-up date. 9. Leave a **final completion note**. 10. Move to **Closed Request**. --- ### Your Core Responsibilities As a Data Feed Specialist, your job on every ticket is to: - Manage the status progression through the pipeline - Complete the initial audit task - Document your work through Notes and Tasks - Move to **Blocked** immediately when progress stops, and notify the submitter - Leave a final completion note before closing --- ### Questions? Use the **HubSpot Assistant (Integration Request bot)** — it's loaded with supporting documentation. If the bot can't answer, reach out to **Tristan Storr** directly. - [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