Twitter and X Feed Widget - Live Timeline or Featured Tweet on Your Store, No API Keys or Developer Account

Your social proof, on the page where it sells

An active feed tells a visitor that there is a real business behind the shop — new stock, replies to customers, an announcement from this morning. This module puts that feed where it does the most good, and it takes about a minute to set up.

No API keys. None. Ever.

This is the point of version 4. Enter your username — paste it with or without the leading @, the module strips it for you — and you are finished. There is no developer account to register, no OAuth flow, no app to create, no keys to paste and no credentials to store, because the module never handles any.

Live timeline, or one featured tweet

Live timeline shows a continuously updating stream of your latest posts. Featured tweet shows one specific post you choose — paste its link and that is the one visitors see.

The second mode is worth knowing about for a practical reason. Twitter/X's public embed service enforces a fairly tight rate limit, and a continuously refreshing timeline can use up most of that quota on its own. Because a featured tweet only ever requests one fixed post, it holds up better when the platform is under load. If you value reliability over automatic updates, that is the mode to pick.

Five placements, chosen on the configuration page

Left column, right column, footer, home page, or a floating button pinned to the bottom-left corner. You pick the spot on the module's own page — there is no trip to Design → Positions, and changing it takes effect immediately.

One thing to be clear about, because it shapes how you use the module: every placement renders a compact button, and the feed opens in a popup when a visitor clicks it. The timeline does not sit inline in your column. That keeps a third-party embed off your critical rendering path, and it means the module never pushes your own content down the page.

Made to match your theme

Light or dark, plus an optional accent colour for links inside the widget. Four further switches hide the header, hide the footer, remove the borders, or make the background transparent — these apply to the live timeline, and the field help says so. Choose a fixed number of tweets from 1 to 20, or a scrolling feed at any height from 200 to 1200 pixels.

For a featured tweet there are two further switches: hide the Show this thread link, and hide photo, video and link previews if you want just the words.

Everything a visitor expects from a tweet

Because this is Twitter/X's official widget rather than scraped text, visitors get the real thing — reply, retweet and like all work natively, exactly as they do on the platform itself. Media, threads and link previews render the way they are supposed to.

Clear validation, and a preview before you publish

There is no guesswork about whether the settings are right. Get something wrong and the save is rejected with a plain-language message — "Please enter a valid Twitter/X username: letters, numbers and underscores only, up to 15 characters", or the equivalent for a malformed tweet link or a bad hex colour — and nothing is written, so a typo cannot quietly replace a working configuration. Once a username or tweet is saved, a live preview on the configuration page shows what visitors will get.

An honest note on customisation

The official widget exposes a light/dark theme and a single accent colour, and that is genuinely all it exposes. If you want to restyle tweet text arbitrarily, no module can give you that through the official embed — it is the trade-off for a feed that needs no API keys and does not break when the platform changes its rules.

Version 4 removed a real security problem

This matters more than any feature. Earlier versions fetched tweets through the Twitter API v1.1 using a bundled, decade-old OAuth library and hardcoded developer credentials shipped inside every copy of the module. Twitter/X shut down free access to that API in 2023, so the integration had stopped working reliably — and worse, those exposed credentials meant an unconfigured install would silently pull someone else's feed by default.

Version 4 removes all of it: no API layer, no bundled OAuth library, no credentials to leak, and nothing left in the module that a platform policy change can break.

Upgrading cleans up after the old version

Open the module and it migrates itself. The old API keys and the legacy settings that no longer apply are deliberately removed rather than left lying in your database. Your username and placement carry over.

Version 4.1.1 also fixed an upgrade fault worth mentioning plainly: the 4.0.1 step tied its success to a registerHook() call returning true, so a transient failure — or a hook already registered by a partial earlier attempt — marked the step failed and PrestaShop disabled the module. The hook is now registered idempotently and the step always reports success.

A privacy setting, and a straight answer about tracking

An optional Do Not Track switch asks Twitter/X not to personalise or track visitors through the widget. Be aware of what that does and does not do: it does not stop the script from loading. This module loads a script from platform.twitter.com on pages where the feed appears, and you should disclose that in your cookie and privacy policy as you would for any third-party embed.

Compatibility

PrestaShop 1.7, 8 and 9, in eight languages: Dutch, English, French, German, Italian, Polish, Spanish and Turkish. Because the feed opens in a popup, every placement relies on your theme's Bootstrap modal — standard on the classic theme and its derivatives, and worth checking on a heavily customised one. The technical module name is unchanged from earlier versions, so existing installs upgrade cleanly.

Frequently asked questions

Do I need a Twitter developer account or API keys?

No. Enter your username — with or without the @, the module strips it either way — and you are done. There is nothing to register and no credentials to store.

What is the difference between the two modes?

Live timeline auto-updates with your latest posts. Featured tweet shows one post you pick, and because it only ever requests that single post it is more resilient when Twitter/X rate-limits its embed service.

Where can I put it, and does the feed show inline?

Left column, right column, footer, home page, or a floating button in the bottom-left corner, chosen on the configuration page. In every case the placement renders a button and the feed opens in a popup over your shop — it does not sit inline in the column.

My feed shows "The live feed could not be loaded right now."

Twitter/X's own embed backend rejected or rate-limited the request. It is not something the module controls, and it usually clears by itself within a few minutes. If it happens often, switch to Featured tweet mode.

Can I restyle the tweets to match my brand exactly?

Only up to a point — the official widget offers a light or dark theme plus one accent colour. That limit comes from Twitter/X, not from this module.

Can visitors reply and retweet from my store?

Yes. It is the official embed, so reply, retweet and like all work natively.

I upgraded from an old version — what happened to my API keys?

They were removed on purpose, along with other legacy settings. The old integration needed credentials that had been publicly exposed for years; the new one needs only your username.

Does it work with GDPR requirements?

There is a Do Not Track option that asks Twitter/X not to personalise the experience, but the embed script still loads. Disclose it in your privacy policy like any third-party embed.