Use Google Drive with Adrails: launch Meta ads from a shared folder
Google Drive is where many teams already keep finished creatives, videos included. You share the folder with your workspace's Google address, Adrails groups its files into ads by subfolder and shape, and builds the Meta launch. Nothing is synchronized in the background.
How the work flows
Google Drive ends where Adrails starts
- Connection
- Folder shared, no Google sign-in
- Reads
- The folders you share, when used
- Best for
- Videos and large batches
Google Drive
Folder shared
- Videos
- 6
- Shapes
- 9:16 and 4:5
- Ads
- 3, two crops each
Adrails
Launch prepared
- Layout
- Ad set per ad
- Daily budget
- $20 per ad set
- Status
- Ready to publish
Meta Ads
Created in the account
- Campaigns
- 1
- Ad sets
- 6
- Ads
- 6
Illustrative values. They show how the work moves and are not customer results.
Step by step
Without Adrails, and with it
What Google Drive already does stays as it is. What changes is everything after it.
| Step | Google Drive alone | Google Drive +Adrails |
|---|---|---|
| Store the creatives | Your team's shared folders. | Unchanged. Files stay in Drive; Adrails only reads the folders you share. |
| Group files into ads | Match each crop to its ad by hand. | A subfolder with hook_9x16 and hook_4x5 becomes one ad with a crop per placement. |
| Get the files into Meta | Upload each video in Ads Manager and assign it to its ad. | Share the Drive folder with the workspace. Its videos are read whole, grouped into ads by subfolder. |
| Build the test | Create the campaign, the ad sets and the ads by hand. | Pick one of three layouts. The agent builds the whole hierarchy. |
| Formats and copy | Crop for each placement and write the text of each ad. | Missing formats are asked for. Copy is written, reused or yours. |
| Before spend starts | Your own check of each screen before Publish. | The whole launch is shown with exact values. New campaigns start paused. |
| Read the results | Ads Manager on one side, store orders on the other. | The Analysis Expert reads Meta results next to Shopify orders. |
| Cut or scale | Edit by hand. Why it changed is not written anywhere. | The Media Buyer prepares it with evidence. An automation can pause what crosses a threshold. |
01
How a shared folder becomes ads
A subfolder holding the same creative in several shapes, such as hook_9x16.mp4 and hook_4x5.mp4, becomes one ad that serves each placement its own crop. A file at the top of the folder is its own ad.
The launch shows every ad with its shapes before anything is created in Meta.
02
Shared folders only, and only when needed
Adrails reads Drive through your workspace's Google address, read-only and limited by Google to the folders shared with it, files added later included. It does not synchronize your Drive: a file is downloaded only when a launch is applied.
Videos are uploaded to Meta a few at a time, and Adrails waits for Drive to report each video's size before sending it.
Sources checked
Common questions
Do I need Google Drive to launch ads?
No. Images, and videos up to 100 MB, can be dropped straight into the conversation. Sharing a Google Drive folder suits larger files and whole batches, and keeps the originals where your team stores them.
Does Adrails see my whole Drive?
No. Adrails reads only the folders shared with your workspace's Google address. It cannot list or read the rest of your Drive, and it never changes, moves, deletes or shares a file.
Does the launch start spending as soon as it is built?
No. The agent shows the account, structure, budget and ads it will create before anything is written to Meta, and new campaigns are created paused until you switch them on.