A template failed to push, or looks wrong in my tool

Why: The email has no Footer (compliance) block. The renderer raises that warning and all four push routes treat it as blocking — HubSpot, Marketo Engage, Pardot and Marketing Cloud alike.

Fix: Add a Footer (compliance) block from the Add tab, fill in Footer text, save, and push again. Landing pages carry no such requirement, so the check is dropped for them.

Why: The tools differ. HubSpot requires its own company name and address variables in every email template and fills them from the portal's email settings, so MarqIQ always writes those and leaves a typed address out. Marketo Engage has no address token at all, so the address has to be typed.

Fix: For HubSpot, set the address once in HubSpot under Settings › Marketing › Email › Footer. For Marketo Engage, type it into Postal address on the footer block, or keep it in Template Studio › Brand Kit so every template carries it.

Why: Custom coded email templates are a Marketing Hub Professional and Enterprise capability. This is a subscription limit on the HubSpot side, not a scope problem, and MarqIQ classifies it from HubSpot's own reply so nobody rechecks permissions that were already correct.

Fix: The refusal lists four routes that work on the current HubSpot subscription: create an email from a template already in the portal, push this same design as a landing-page template, export the HTML for another sending tool, or upgrade the portal. Landing-page templates are not tier-gated.

Why: The private app token is missing a permission the write needs. HubSpot also answers 403 for a plan limit, so MarqIQ reads the reply before deciding which of the two it is.

Fix: Template and page writes need content. Creating a marketing email needs content or marketing-email. Image upload needs files. Open your MarqIQ private app at app.hubspot.com/l/private-apps, tick the scope under Scopes, and save. Then reconnect HubSpot under Integrations and push again.

Why: The stored credential has expired or been revoked. HubSpot answers 401. Pardot answers 401 because Salesforce OAuth tokens expire. Marketo Engage fails at the authentication step and the trail says so.

Fix: Reconnect that tool under Integrations, then push again. Copy a fresh HubSpot token from the private app at app.hubspot.com/l/private-apps. Generate a new Pardot access token and refresh token from your Salesforce Connected App — Salesforce documents the steps at help.salesforce.com/s/articleView?id=sf.connected_app_create.htm. Take the Marketo Engage Client ID and Client Secret from Admin › Integration › LaunchPoint › your MarqIQ service › View Details. The template itself is untouched by a failed push.

Why: Content Builder enforces unique asset names per folder, and an asset there that MarqIQ has no record of already has this template's name.

Fix: Rename the template in MarqIQ and push again, or delete the old asset in Content Builder first. MarqIQ repeats Marketing Cloud's own wording so you know which name it objected to.

Why: Marketo Engage blocked it with a business rule. Pushing a template a second time is no longer a cause: MarqIQ updates the template it pushed before, and gives a new one its own suffix when the name is taken. What remains is a source template that is not approved yet, or an email or page name already used in the destination folder.

Fix: If the trail points at the source template, approve that template in Marketo Engage first. If it stopped at creating the email or page, rename it in MarqIQ or remove the earlier one from the destination folder, then publish again.

Why: Marketo Engage cannot take a condition from a template. Its script language only runs inside an email script token, and written into the body it would be printed to the reader. MarqIQ pushes the block without the condition and says so above the canvas.

Fix: Open the email in Marketo Engage, select the block and make it dynamic with a segmentation, which is how Marketo Engage shows content to some people and not others.

Why: This affected templates pushed before October 2026: those blocks were written as HubSpot image and button modules, which do not hold the markup MarqIQ sends.

Fix: Push the template again. Every block now arrives as an editable rich text module with the picture or button inside it.

Why: Marketo Engage refused a folder operation at that point in the tree. Some instances block folder creation at the root by API.

Fix: Create the folder by hand in Design Studio at that location. MarqIQ finds it and uses it on the next push.

Why: MarqIQ places a template beside the one it was cloned from, and failing that in the folder where most of your templates of that type already live. Marketo Engage reported neither, and MarqIQ never creates a Design Studio folder of its own.

Fix: Create any template of that type in Design Studio once, anywhere sensible. Every push from then on uses that folder.

Why: The create call worked and the approve call did not. Marketo Engage only offers approved templates when a marketer creates an email or a page, so the template exists and cannot be chosen.

Fix: Open Design Studio, find the template by the id in the banner, and approve it there.

Why: Neither tool offers an API that creates a landing page. Pardot's API v5 documents no landing-page creation, and CloudPages has no generally-available creation API. MarqIQ refuses the push and says which limit it hit.

Fix: Click Export HTML and paste the file into the Pardot landing page builder or into CloudPages. The download is identical to what a push would have sent, because preview, export and push run through one renderer.

Why: The two upload routes have different limits. HubSpot takes up to 5 MB as PNG, JPG, GIF, WEBP or SVG. Marketo Engage takes up to 4 MB as PNG, JPEG, GIF or WebP, and refuses SVG outright.

Fix: Re-export the image within the limit for that tool. For a Marketo Engage template, convert an SVG to PNG at twice the display width.

Why: Neither tool accepts an image upload from MarqIQ, so there is nowhere to put the file.

Fix: Host the image somewhere your recipients can reach and paste the https URL into the field.

Why: The request did not complete — a network drop, or a call that ran past its time limit while your tool was still working.

Fix: Check the destination folder in your tool before pushing again. The asset may already be there, and a second push would create a duplicate or fail on the name.

Why: A file can exist and still not be registered as a template that is available for new content. Until it is registered, the Design Manager shows it and the creation flow never offers it.

Fix: MarqIQ reads the registration back after every push and corrects it when HubSpot got it wrong. If the banner still says HubSpot has not confirmed it, it quotes HubSpot's reason — fix that and push again.

Why: Saving new blocks or settings after a push resets the status, because the copy in your tool is now behind. In tool means the two match, and nothing else.

Fix: Push again. Nothing is wrong with the copy in your tool. It is the older version, and the chip is telling you so.

Why: Outlook for Windows ignores media queries. MarqIQ stacks columns at 480px using the standard responsive-email pattern, and Outlook does not run it.

Fix: Design the two-column row to be readable at half width. For anything that must stack, use two full-width rows instead.

Why: The same reason — the mobile rules that hide and show it are media queries. The builder says so under the control when you choose Mobile only.

Fix: Do not rely on device visibility for anything a recipient must not see. Use it for a shorter mobile headline, not for hiding a price.

Why: Most mail clients cannot load a web font, so the fallback in the stack is what actually renders. The Brand Kit therefore offers six email-safe stacks only, and says so on the page.

Fix: Judge the design on the fallback. Open Template Studio › Brand Kit and read the sample pane on the right, which renders through the same engine as your live templates.

Why: Your Brand Kit is locked. When it is locked the per-template Brand colour is ignored entirely, and every render — preview, export and push — uses the kit's primary colour, buttons and form submit buttons included.

Fix: Leave the lock on if that is what you wanted. To let a campaign use its own tint, clear Lock the brand at Template Studio › Brand Kit, then push the template again.

Why: The logo address is not one a mail client can reach. MarqIQ requires an absolute address on save for exactly this reason — a relative path resolves against nothing in an inbox — but an address that merely stops working later will still break.

Fix: Open Template Studio › Brand Kit and paste an https address into Logo URL (https). Open that address in a private browser window first. For images in blocks, use Upload on a HubSpot or Marketo Engage template so the file lives in your own tool's store.

Why: Gmail truncates a message at about 102 KB. Anything past the cut is hidden behind a link, and the footer is at the bottom.

Fix: Watch Estimated size in the builder. It measures the tool-ready HTML and turns red past 100 KB. Cut Custom HTML blocks, remove repeated sections, and move long copy onto a landing page. Image files do not count — only the markup does.

Why: Email clients drop CSS margins, so MarqIQ writes every Space around (px) value as padding on the wrapping table cell. A client that adds its own padding on top of that is adding to a value MarqIQ set, not replacing it.

Fix: Adjust Space around (px) in the Layout section rather than adding Spacer blocks, and re-check in the mobile preview at 375px.

Why: An email previews at 680px on desktop and renders at 600px. The preview is deliberately wider so the template's own mobile breakpoints do not fire early and falsely collapse side-by-side sections.

Fix: Use the mobile preview at 375px to judge the narrow end, and read the <your tool> code tab for the real widths. Column widths in an email are written as both a width attribute and a style, because the attribute is what Outlook obeys.

Why: MarqIQ writes a Custom HTML block verbatim into the file it sends. What happens to it afterwards is your tool's own behaviour, and MarqIQ has no control over it.

Fix: Compare the <your tool> code tab against what your tool shows. If the two match, the difference was introduced by your tool and belongs in its own editor. If they differ, tell support which block and what changed.