The level of tracking detail depends on your configuration. While the parent module enables the link, the Acquia DAM – Enhanced Integration Links submodule is required for deep-link visibility.
Feature | Acquia DAM parent module | Enhanced integration links submodule |
Tracking level | Media Entity level | Content Entity level |
What is tracked? | Tracks the Media item itself, such as /media/1/edit. | Tracks every specific page/node where that media is used. |
Visibility | Shows that a Media entity exists in Drupal. | Shows every Node, Paragraph, or Block where the asset is embedded. |
Best for | Basic asset inventory. | Comprehensive dependency mapping and audit trails. |
Review the status dashboard to check total assets, registered links, and remaining assets by media type.
Review the completion summary to check media items queued, content entity references queued, and queue items processed.
The feature supports three Drush commands for different workflows:
Performs the complete workflow: queues assets and processes them immediately.
Command syntax:
drush acquia-dam:register-integration-links [--batch-size=<number>] [--media-type=<type>] [--process-limit=<number>]
Options:
--batch-size: Number of assets to process per batch. Default: 50.
--media-type: Process only a specific media type.
--process-limit: Maximum queue items to process. Default: 0 (no limit).
Examples:
drush acquia-dam:register-integration-links
drush acquia-dam:register-integration-links --batch-size=100
drush acquia-dam:register-integration-links --media-type=acquia_dam_image_assetRecommended Usage:
Ideal for small to medium datasets or manual one-time operations.
Discovers assets and adds them to the queue without processing. Useful for large datasets or decoupled workflows.
Command syntax:
drush acquia-dam:queue-integration-links [--batch-size=<number>] [--media-type=<type>]
Examples:
drush acquia-dam:queue-integration-links
drush acquia-dam:queue-integration-links --media-type=acquia_dam_video_assetProcesses items already queued and provides controlled batch execution.
Command syntax:
drush acquia-dam:process-integration-links-queue [--process-limit=<number>]
Examples:
drush acquia-dam:process-integration-links-queue
drush acquia-dam:process-integration-links-queue --process-limit=100Integration links are automatically registered when:
The registration happens through Drupal's queue system. Cron processes the queue automatically with no manual action required for ongoing maintenance.
To manually trigger queue processing:
drush cronOr process the specific queue:
drush queue:run acquia_dam_integration_linksYou can re-run the registration process at any time. The system automatically skips assets that already have registered links, which prevents duplicates.
When to re-register:
Issue | Solution |
"Queue is empty" but assets show as remaining | Run the register integration links command: |
Processing is slow or times out | Use smaller batch sizes: |
Enhanced mode not detecting content entities | Clear cache: Verify sub-module is enabled: Re-run registration. |
Automatic maintenance:
Cron handles ongoing registration automatically. New or updated assets are queued and processed during scheduled Cron jobs without configuration changes.
Large sites:
For sites with many assets, use the decoupled workflow: queue assets first with queue-integration-links, then process in controlled batches with process-integration-links-queue. Schedule large operations during off-hours to minimize performance impact.
Enhanced mode:
Enable the Enhanced integration links sub-module early in your implementation for complete tracking. After you enable it, re-run the registration to catch existing content entity references.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.