
As an ad agency running campaigns for several provincial clients, we use Flashtalking mainly for ad serving and trafficking HTML5 display creative. The most valuable part has been the handoff from production to live. Our banners are built in Google Web Designer and then uploaded to Flashtalking, where we can QA every size in one place before anything goes out. That catches broken clicktags, file-weight issues and missing backups before the media vendors do, which saves us a lot of back-and-forth.
The shareable preview links have also become part of how we work with clients. Instead of sending zip files or screenshots, we send one link where the client can see every size working the way it will in market. Approvals are faster and the feedback is clearer.
On the reporting side, having impressions, clicks and engagement in one dashboard across placements means we can pull results for client reporting without chasing numbers from each publisher.
An unexpected benefit: having everything stored centrally makes it much easier to version and refresh creative mid-campaign. Swapping in a new message or date across a full set of sizes is quick, not a rebuild. Review collected by and hosted on G2.com.
The biggest pain point for us is that Flashtalking sits at the end of a long production chain. Our creative typically moves from Illustrator to Figma to Google Web Designer before it ever reaches Flashtalking, so the platform doesn’t really help with building the ads themselves. Each handoff adds time and another chance for something to break. A smoother path from design tools straight into Flashtalking would cut a lot of steps for agencies like ours. The Figma plugin is a step in the right direction, but it still needs to cover more of the build.
The interface can also feel dense for people who don’t use it every day. Finding the right setting or report sometimes takes more clicking than it should, and newer team members have a real learning curve before they’re comfortable trafficking on their own.
Upload and QA error messages could be clearer too. When a file fails a spec check, the reason isn’t always obvious, so we end up troubleshooting by trial and error. Plain-language explanations with a suggested fix would save time. Review collected by and hosted on G2.com.


